Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Managing build numbers for multiple jobs of same stage


We have large code base that gets built in Bamboo. We typically make multiple builds: one for debug configuration and another for release configuration. After a build passes verification, it gets deployed to artifactory under a directory with build number (something like newyork/beta/ where 1546 is build number and newyork/beta is release code name).

Currently we have one job (in one stage) that makes a build for say debug configuration. Then we change a flag and start new build to make build for release configuration.

We are looking for ways to make both release and debug builds in one attempt. We can clone current job in the same stage. First job builds debug and 2nd one for release. The jobs can run in parallel which is great.

The challenge is how do I derive unique build numbers so that debug build can to its own folder on artifactory and release build of its own.

Lets say Bamboo environment gives me buildnumber is 10. Lets say I assign 10 to debug build and 11 for release build. Next time the plan runs, Bamboo will give me 11 instead of 12. 

We don't want to use same build number for both Debug and Release.

I appreciate recommendations for an elegant solution.


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events