As a result of our testing of the Bamboo upgrade from the current 5.7.2 version to the latest Bamboo version 5.12.2, we have run into a major issue: builds won’t get triggered from the Bamboo UI and log the following System Error:
Bamboo has detected one error.
LESA - SVC - 06.b content-admin-service - Unit Tests : Error encountered while triggering manual build: Could not generate next build number for 'LS-CSVCUT'
(16 Jun 2016, 9:27:07 AM, Occurrences: 2)
When viewing the error log, one can see the reason for the failure:
java.lang.RuntimeException: Could not generate next build number for 'LS-CSVCUT'
Caused by: java.lang.IllegalStateException: No build numbers record for plan LS-CSVCUT
The reason behind is quite obvious: the new DB table BUILD_NUMBERS being empty (as a result of the DB changes specific to the upgrade) does prevent all builds from generating the next build number. I do not recall any specific database instructions in the Bamboo upgrade steps by Atlassian that suggested a data migration: did we miss something and, if so, what should be done – as a pre- or post-upgrade – in order for that to be fixed and not become a show stopper? Does Atlassian have any data migration plan that should be followed during the upgrade procedure?
This is a blocking issue for us at this moment and your assistance/advice will be much appreciated.
Thank you in advance for a prompt response.
Wolters Kluwer Health
4600 S Syracuse St, Suite 1200
Denver, CO 80237
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs