You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Bamboo Server 6.1.1
Doing a build then auto firing a release to dev server.
On the deployment we've been using the Release Versioning tool that is provided within Bamboo.
We've been using it for months then all the sudden our versioning has changed.
What we have in the text field for releases is `0.0.${bamboo.buildNumber}`
what we are getting is `0.0.***_(2)`
When we hard code a release as `0.0.95` we get `0.0.95_(2)` So it's not the variable.
See screen cap for all release variable setting page.
The problem is I don't know where to go to turn off whatever this is, and no one remembers turning anything like this on. It is not reflected any where else that I can find outside of releases, the builds and deploys don't include it anywhere that I can find.
That happens if a release with identical name already exists. This might be because particular trigger configuration you currently have or because the deployment was linked to different build plan before.
Thank you this is the correct answer! Wish this was more clear in the release versioning page.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.