Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,551,881
Community Members
 
Community Events
184
Community Groups

Bamboo Release Version is appending (2)

Erik Anderson
Erik Anderson May 31, 2019

We have a plan that recently started appending (2) to the release version e.g. 1.0-BUILD9_(2)

Our release version is set to ${bamboo.maven.version}-BUILD${bamboo.buildNumber} and the ${bamboo.buildNumber} is BUILD9.

What could be causing it to append a (2) to the release?

Answer
Watch
Like Be the first to like this
238 views

1 answer

0 votes
Jimmy Seddon
Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Jun 03, 2019

Hi @Erik Anderson,

Welcome to the Community!

Anytime I have seen that happen it has been because someone tried to create a release with the same name/number as a release that already exists.  You should check to make sure that someone isn't creating multiple releases from the exact same build.

I hope that helps.

-James

Reply

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS
AUG Leaders

Atlassian Community Events

See all events