You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Support,
we have an app who uses their Release number in following format: 10.20.30.40, where 40 is the build#, 30 minor release#, 20 major release# and 10 the main application version. Now, when we use a ${bamboo.buildNumber} variable for the build, it works fine and also increments properly as expected with every subsequent build. Even the minor release# also gets increased automatically when it is a new release. Eg, a subsequent Build# will be: 10.20.30.41 and a subsequent release will be 10.20.31.41 …. but we wouldlike to have more granular control. So, do you think we could use a scheme such as: ${bamboo.appVerNumber}.${bamboo.majorRelNumber}.${bamboo.minorRelNumber}.${bamboo.buildNumber} after initializing the variables as appVerNumber=10, majorRelNumber=20, minorRelNumber=30 and buildNumber=40 in the aforementioned example? Thank you.