Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Is bamboo adding things to my release number?

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. 

Screen Shot 2018-07-16 at 5.36.32 PM.png

 

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. 

1 answer

1 accepted

1 vote
Answer accepted
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 17, 2018 • edited

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. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events