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.
update dbo.BUILD set NEXT_BUILD_NUMBER=346 where FULL_KEY in
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?
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.
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 (
FROM [bamboo].[dbo].[BUILD] where FULL_KEY in (list of FULL_KEYs)
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events