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,558,955
Community Members
 
Community Events
184
Community Groups

Changing buildnumbers or reseting build numbers

lance_lyons
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 03, 2018

Hi,

We have scenarios where with branching and moving to hotfix branches that we want to continue buildnumbers that where on a master branch (3.00.00.345) and when we move to a hotfix branch we want to continue down the same line of build numbers (3.00.00.346, 347) etc.

In the past we had to do this with direct db updates.

ie,

update dbo.BUILD set NEXT_BUILD_NUMBER=346 where FULL_KEY in
(
'SCM-OMHTS',
'SCM-OMHTS-BMADMIN',
'SCM-OMHTS-JOB1',
'SCM-OMHTS-ODBM'
)

 

This was easily done in Teamcity inside the buildserver UI.  Bamboo was not able to do that.

 

Now that the dbo.BUILD table has changed,  what is the recommended approach to changing the builds numbers?

 

Thanks

Lance

2 answers

0 votes
lance_lyons
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 15, 2018

Yes that looks correct.  I was able to figure this out on my own.   The one suggestion is that the Bamboo db now uses case sensitive collation so table names and column names must match case wise.

 

 update  [bamboo].[dbo].[BUILD_NUMBERS] set NEXT_BUILD_NUMBER= 871
 where BUILD_ID in (
  SELECT [BUILD_ID]
  FROM [bamboo].[dbo].[BUILD] where FULL_KEY in  (list of FULL_KEYs)

0 votes
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 04, 2018

Hi Lance,

Could you please confirm if the instructions found in the  "Unable to change the current build number in Bamboo" KB were useful? It will be helpful to have your confirmation publicly available here to help other community members. 

thanks

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events