Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo Release Number using Variables

Hi Support,

we have an app who uses their Release number in following format:, 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: and a subsequent release will be …. 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.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events