How can I uniquely identify a build?

To my surprise and consternation, Bamboo's build numbers are not globally unique like TeamCity's are. How can I uniquely identify a build so that I can set that value in the build position of my version number (1.2.3.build)? There are a variety of variables I could use but many of those could change if a plan or job was renamed.

I've currently settled on a concatenation of the build number and the first seven characters of the git hash. To get there, I have to read the base version from a file, write it back with the build number, write it to a file, then import it using the import variables task so that it is available to later tasks. There's got to be a better way.

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

335 views 0 8
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you