Allow building off a Git Tag about appcenter HOT 99 OPEN

+1000 Being able to go to an application, build and then being able to either build from:
a) branch
b) tag
c) commit hash

is mega important! At the moment we only have option a) whereas a lot of other CIs offer all three.

from appcenter.

Bad bot! We want this.

from appcenter.

I'm also looking forward to seeing this feature in App Center. Being able to build multiple versions of an application from the same numbered GitHub tagged release in AppCenter would be a high-value feature.

from appcenter.

Hi! we are a customer of app center and are in dire need of this feature! Any help would be appreciated

from appcenter.

🤘
Let's add some reactions with 👍 on the main message!!@!

It's 171 likes at the point

from appcenter.

Is this really this hard change?

from appcenter.

+1 the same with git flow.

from appcenter.

Glad to say I'm the 200th to be sad to chose Microsoft

from appcenter.

Hi @talsemgeest, thanks for this feature request! I can see how this would help in your workflow. We'll keep this request open to track additional interest.

from appcenter.

this is my hacky workaround incase it helps others until this feature is implemented. for context my infra pushes tags on master, so there is also a corresponding commit message i.e. "master: v1.0.9" and the tag would be "v1.0.9" and we have a package.json with a corresponding "version": 1.0.9 in the root of the project

what i am doing is in my post-checkout script

PACKAGE_VERSION=$(cat package.json \
  | grep version \
  | head -1 \
  | awk -F: '{ print $2 }' \
  | sed 's/[",]//g' \
  | tr -d '[[:space:]]')

## if build filter and last commit doesnt contain filter cause failure
if [ "${BUILD_FILTER}" != "" ]; then
  if [ "$(git log -1 | grep -u $BUILD_FILTER)" == "" ]; then
      exit 1;
  else
      git checkout v${PACKAGE_VERSION};
  fi
fi

where BUILD_FILTER is a param provided to the appropriate release branch you would like to enforce a tag checkout, so in my case BUILD_FILTER="master: v"

An FYI though exit 1; only stops the majority of the build process, the rest of your custom build scripts still run, i am accounting for this in each build. The proper way to address is found here https://stackoverflow.com/questions/60329968/how-to-fail-a-appcenter-build-on-script-exit-code

Now this is far from perfect..... but itll do for now

hope it helps someone else :)

good luck!

from appcenter.

+1. 2 years past, it's still not supported?

from appcenter.

I thought for sure AppCenter would have this by now. I too want to be able to trigger a Build only when the commit has a tag that matches a regex. While a post-clone script could be used to work around this limitation, it would mean nearly all commits would trigger a build that would fail, wasting hundreds of build minutes a month.

from appcenter.

I know numerous companies that have this within their CI/CD process. It's really surprising we can't get this with App center

from appcenter.

I came looking for app center support for tagged releases, so it's a +1 from here.

from appcenter.

👍

from appcenter.

this would be an amazing feature if we can get this!

from appcenter.

+1

from appcenter.

👍 yes need this!

from appcenter.

I really need this.

from appcenter.

We need this!

from appcenter.

This would be a nice addition

from appcenter.

Please, add this!

from appcenter.

+1

from appcenter.

+1

from appcenter.

any update on this one?

from appcenter.

There is API support for building off a specific commit: https://openapi.appcenter.ms/#/build/builds_create

Would that work as a workaround?

from appcenter.

+1. With other CIs I've always managed release deployments using a tag rather than a new branch. Would love to see this in App Center 😄

from appcenter.

+1 Not being able to build from a tag has been forcing us to change our workflow

from appcenter.

+1 for this feature. Thank you.

from appcenter.

+1. Is this feature being worked on at all?

from appcenter.

+1

from appcenter.

@tindn, we post our iteration plan each month. This issue is not being worked on in this month's plan.

from appcenter.

+1

from appcenter.

how did this happen!

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

We use gitflow and create a release branch per release (release/release-1.x) Would be great to build from these without having to manually clone each release branch up with the required config

from appcenter.

👍

from appcenter.

Another +1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

I'd really like this feature, especially if one could set up wildcard rules. E.g. build all commits tagged release/* and latest. We maintain multiple versions of our software and the master branch is never released directly.

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

yes please

from appcenter.

another yes please

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1 more

from appcenter.

For a specific use-case, I use lerna to version two react-native apps and would like to be able to build only on tags that match the format ^app-1@\d.\d.\d$.

from appcenter.

+1

from appcenter.

I would very much like to see this feature implemented as well.

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

Any updates on this?

from appcenter.

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

from appcenter.

+1

from appcenter.

any updates?

from appcenter.

It's weird they cannot add such small and so desired feature 😕

from appcenter.

waiting for 2 years for this feature.

from appcenter.

are we there yet?

from appcenter.

We absolutely need this! please make it happen :(

from appcenter.

+1

from appcenter.

Hi there! Thanks for your interest in the feature! Please use reactions instead of +1.

from appcenter.

Yeah, but we're using +1 to beat the evil @msftbot 🤖

from appcenter.

+1

from appcenter.

Hi there! Thanks for your interest in the feature! Please use reactions instead of +1.

from appcenter.

3 years and this is still pending, many workflows depend on tag releases.

from appcenter.

I made my own CI/CD with Circle CI
Because if it depends on this lib here, we die and it won't be done

from appcenter.

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

from appcenter.

Is there any updates on the timeframe for when this feature will be either looked at or added?

from appcenter.

+1

from appcenter.

+1

from appcenter.

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

from appcenter.

Not stale

from appcenter.

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

from appcenter.

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

from appcenter.

Not stale. Still needed

from appcenter.

+1

from appcenter.

+1

from appcenter.

+1

from appcenter.

This is one of the most high impact features you could ask for.

This is almost a requirement if AppCenter wants to provide better build support for monorepos

from appcenter.