Allow building off a Git Tag

[talsemgeest]

What App Center service does this feature apply to?
Build

Describe the solution you'd like
We use Gitflow as our branching strategy, and in Gitflow every release is tagged on the master branch. I would like to be able to build off those tags, rather than always building off the HEAD of the branch.

Describe alternatives you've considered
A workaround is creating a new branch off each tag you want a build config for and setting it up as a new build config in AppCenter, which is time consuming.

Additional context
We have multiple customers on different versions of our (white label) app, so being able to build different versions is a must for us.

[nilofer]

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.

[zob]

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

[jjhampton]

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.

[shakibbzillow]

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

[MattMasters]

👍

[ralesiupgrade]

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

[rogueturnip]

+1

[dgobaud]

👍 yes need this!

[MichaelObi]

I really need this.

[andyheninger-awh]

We need this!

[gdebbe]

This would be a nice addition

[Juansero29]

Please, add this!

[thilina-noetic]

+1

[daveokeeffe]

+1

[grevolution]

any update on this one?

[dennispan]

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

Would that work as a workaround?

[andrejacobs]

+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.

[jacobhummel]

+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 😄

[topes]

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

[ducpt2]

+1 for this feature. Thank you.

[tindn]

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

[martyu]

+1

[nilofer]

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

[troyanas]

+1

[morgondag]

how did this happen!

[nadjibus]

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

[LeonardoFassini]

+1

[AnastasiaKubova]

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

[chrisarts]

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

[charleston10]

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

[ghost]

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.

[emech-en]

Is this really this hard change?

[arindoneATK]

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

[s-bridges]

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

[mljlynch]

+1

[hauserkristof]

+1

[ghost]

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.

[dri-richard]

Not stale

[ghost]

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.

[mljlynch]

Bad bot! We want this.

[thibaultcapelli]

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

[microsoft-github-policy-service]

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.

[kitingChris]

Not stale. Still needed

[pauluhn]

+1

[kumkao]

+1

[donald-boosted]

+1

[araphiel-nf]

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