Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×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
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)
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.