bamboo adding _(2) to build version

Bamboo is adding _(2) to a build version, and I cannot figure out where or why, can anyone advise?

From the deploy log, you can see Bamboo has added this to the build name right at the start of the log.  This deploy is supposed to then push the built docker container (built in previous stage) into Nexus, but it fails because Nexus will not accept the "_(2)" suffix.  The previous build stage worked with no mention of this deploy version addition.

 

simple 01-Dec-2016 14:38:46 Build Deployment of 'develop-10_(2)' on 'Nexus' started building on agent bagent01
simple 01-Dec-2016 14:38:46 Remote agent on host bagent01
simple 01-Dec-2016 14:38:46 Build working directory is /home/bamboo/bamboo-agent-home/xml-data/build-dir/13271045-13172742
simple 01-Dec-2016 14:38:46 Executing build Deployment of 'develop-10_(2)' on 'Nexus'
simple 01-Dec-2016 14:38:46 Starting task 'Clean working directory task' of type 'com.atlassian.bamboo.plugins.bamboo-artifact-downloader-plugin:cleanWorkingDirectoryTask'
simple 01-Dec-2016 14:38:46 Cleaning working directory '/home/bamboo/bamboo-agent-home/xml-data/build-dir/13271045-13172742'
simple 01-Dec-2016 14:38:46 Finished task 'Clean working directory task' with result: Success
simple 01-Dec-2016 14:38:46 Starting task 'Check out bamboo deployment tools' of type 'com.atlassian.bamboo.plugins.vcs:task.vcs.checkout'
simple 01-Dec-2016 14:38:46 Updating source code to revision: 4dcce3f40a22f0cf3eed0ae469e83c8d803056a8
simple 01-Dec-2016 14:38:47 Updated source code to revision: 4dcce3f40a22f0cf3eed0ae469e83c8d803056a8
simple 01-Dec-2016 14:38:47 Finished task 'Check out bamboo deployment tools' with result: Success
command 01-Dec-2016 14:38:47 Substituting variable: ${bamboo.planKey} with SRV-RW38
command 01-Dec-2016 14:38:47 Substituting variable: ${bamboo.buildNumber} with 10
command 01-Dec-2016 14:38:47 Substituting variable: ${bamboo.deploy.version} with develop-10_(2)

 

This was an automated build triggered from a code update; a previous manual deploy of the same build worked successfully with the deploy version being set correctly to develop-10.

3 answers

1 vote

Hello Helen,

This was an automated build triggered from a code update; a previous manual deploy of the same build worked successfully with the deploy version being set correctly to develop-10.

Based on the statement above, you already had a develop-10. And since you cannot have duplicate release names, Bamboo has appended something to the release version name.

Bamboo does that to prevent having the same release name

image2016-12-2 14:18:32.png

Kind regards,
Rafael P. Sperafico

Thanks Rafael, you're right in that there was already a develop-10 - but then why didn't it automatically increment to develop-11?  We do have that option ticked, as per your screenshot, and some builds do increment  correctly, as we have develop-1, develop-2, develop-3 etc.  This has happened 3 times now, on develop-5, develop-7 and develop-10.  Can you suggest where I could look (I can't find a log file for this) that would detail why the release number wasn't just incremented to develop-11 - why did it keep develop-10 but add the "_(2)" to the name?

Hello Helen,

I would suggest you on raising a Support Request, so we can review which Bamboo version you are running along with the way build plan / build branch(s), triggering and deployment are set up.

If possible, could you please mentiion this thread when raising the support requets, so we can do a follow up, so other facing the same issue can benefit from resolution given in support request.

Kind regards,
Rafael P. Sperafico

0 vote

Any update on this issue, I am having the same problem, after removing and re-adding a plan branch. I'd like to revert to the plain naming and count prior to removing and adding the plan branch.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,801 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you