Unique Build Number per workflow

Question & Answer
1

What would be the best practice for setting a unique build number for each workflow? I saw this similar question (Global variable incremented in every build) suggesting storage in an external file, but that thread is pretty old so I’m wondering if there is an easier way to do that now.

The reasoning is that we have 2 separate workflows in the same app:

  • Alpha (release a tester build to Fabric)
  • Release (upload a build to TestFlight where we will submit to app store)

We would like both of these to have build numbers tracked separately so that running Alpha increments Alpha’s build number, but not Release’s (and vice versa).

2

Thanks for the question @jwright!

The things described at Global variable incremented in every build still apply. There’s no built in support for this use case as our recommendation is to use a unique build number for every build, regardless of the branch / workflow, as described at https://stackoverflow.com/questions/33821137/build-versioning-in-continuous-delivery/33821876#33821876

If you have any questions just let us know! :slight_smile:

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.