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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,459,360
Community Members
 
Community Events
176
Community Groups

Can I edit the Bamboo build number?

Hi,

I am evaluating options for encoding the sprint/iteration no. into the 4th digit of our software version scheme.

Is there a way in Bamboo's plan configuration where I set the offset for the Bamboo build number before the next build starts?

Many thanks in advance!

Frank

 

3 answers

1 accepted

3 votes
Answer accepted

Update: please see our knowledge base article for the updated workaround.

Also if you want to track the progress of our work on this suggestion watch/vote on BAM-10282.

 

I'm not sure if I understood your question correctly, but if you're asking if you can change the "next build number" for a plan or branch then it only possible by direct DB manipulation:

UPDATE build SET next_build_number = X WHERE full_key = <your-plan-key>

warning Please make sure you create full DB backup before executing any manual modifications.

Thank you for the immediate answer. The SQL statement will do exactly what I was looking for, but I hoped this would also be supported in the Web-GUI, which is - as you write - obviously not the case.

Is this still the best way to do this?

 

I see some suggestion on the Internet that the build number cannot be lowered but must always be raised.

Is that true?

Thanks for this information @Krystian Brazulewicz  ; Please note that  Bamboo schema has changed since this post.

I  use Atlassian Bamboo version 6.8.1 .

I am describing what I did to achieve same effect with new schema I so it may save time for others .

The table that maintain build numbers in  newer versions of Bamboo is called "BUILD_NUMBERS" 

To make a determination  of per plan next build number corresponding to title or from plan key I used this join 

"select TITLE, FULL_KEY, BUILD.BUILD_ID , BUILD_NUMBERS.NEXT_BUILD_NUMBER from BUILD, BUILD_NUMBERS where BUILD_NUMBERS.BUILD_ID=BUILD.BUILD_ID;"

And then to update BUILD_NUMBERS - I ran following query 

UPDATE BUILD_NUMBERS SET NEXT_BUILD_NUMBER = <desired build number> WHERE  BUILD_ID =<plan id  for your plan that you figured from above query >

 

Like Daniel Santos likes this
Like yogesh_devi likes this

I also tried a third party plugin # Build Number Manager for Bamboo available on atlassian marketplace and that helps me solve my purpose.

This plugin provides a feature called  "Enable plan / branches build number synchronization" that can be enabled or disabled on  any build plan

When turned on this  feature ("Enable plan / branches build number)  causes  every branch build on the particular build plan  to have unique build number that increments from the highest build number in plan branch.

So for example if your plan branch has build number 555 when you enable this feature, and then you build on another branch in that plan . In that case the branch build will have a build number 556 or more. In other words the increment in build number transcends all branches ( not just the plan branch ) .  While this is useful in ensuring every build on a plan has a unique number regardless of branch - it causes build number skyrocket on a large team  so has to be used with discretion.  And also the plugin comes with a price tag

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events