How to separate the build counter used globally so that a specific workflow e.g. release does not increment when a CI build is run?
1 Like
Hi @cbramley,
Thanks for asking this here! 
May I ask why you’d need this? I might not see the full picture here, but for me it seems to be a bad idea to increment it on some branches but not on others.
You’re referring to the BITRISE_BUILD_NUMBER by build counter right?
One of the most important factor of the BITRISE_BUILD_NUMBER is that it’s the same value as the one you can see on bitrise.io
Not incrementing it would result lots of duplicate build numbers on the UI.
If you can clarify a bit what the use case for this would be we can provide more info. From what you wrote I think you might be interested in this discussion:
In any case, if you have any questions we’re always happy to answer here! 
Hi @viktorbenei
It could be that I’m trying to do something a little unusual here. Essentially I want to match the BITRISE_BUILD_NUMBER to my release candidate build number as that branch is built far less often. In order for that to work as planned the CI builds need to be tracked elsewhere.
That discussion you linked was very helpful, it should allow me to do exactly what I need, thanks!