I'm looking for a way to create a unique semantic version number across multiple plan branches within one plan. E.g. I have a plan to build Git feature branches. I want each feature being built to get a unique version number. I was using the following setup first:
The alphaVersion is set manually (e.g. related to a development sprint). The problem with this, though, is that each plan branch starts its own build numbering and thus we will have overlapping version numbers.
I have tried postfixing the number with
but this makes the the version number too long, since we're using Octopus Deploy which will only accept version numbers with a maximum length of 20 characters. This could only be a viable solution if I was able to use a substring of this variable's value. But that seems impossible in Bamboo.
I hope someone can help!
Thanks for your feedback, Xabier. I have been diving a bit more into this and ended up in using the following format for now:
I have indeed used the "Inject Variables from file", with a script to extract the JIRA issue number from the branch name, as described in my related question here.
The other annoying part of this, is that Bamboo generates its own release number following a non-customizable format. But at least the whole chain works now.
I have been fighting with similar issues for a while, my solution so far is to add the branch name to the version:
Not sure this will end up fitting in 20 chars anyway.
Other possible option would be, in the first job of your build, trim the revision number, save it to a file, and inject the variables , defining the scope as the full plan. A bit cumbersome, I know
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot