Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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.

Atlassian Community about banner
Community Members
Community Events
Community Groups
  • Community
  • Products
  • Bamboo
  • Questions
  • How to change default (from bamboo deployments) of "Releases from branches will default to using the branch name suffixed with the build number of the build result"

How to change default (from bamboo deployments) of "Releases from branches will default to using the branch name suffixed with the build number of the build result"

Ron Chan Rising Star Mar 04, 2014

Would be extremely helpful and just plain logical for the "Release Version" to apply for all branches of a particular build plan.

We release from different release branches (with the JIRA ticket integration e.g. release-XPROJ-1, release-XPROJ-2).

It seems that Bamboo deployments was created with the mindset there would only be a single release branch and I don't believe most folks do things that I wrong?

7 answers

0 votes

That options is coming in Bamboo 6.1

@Marcin Gardias  - has this option come in yet. Can you please provide documentation if possible 



Same here! It sucks that we have to manually change the release version when deploying a specific branch (besides master)... Why isn't it just "inheriting" the master settings... or even being able to set our own config.

Same here, this will be a major problem for us and will only build a stronger case to use Jenkins

We have the same problem of course. Is there a plan to fix this?

0 votes
Ron Chan Rising Star Apr 03, 2014

And I keep wondering, if you're a company that uses Bamboo Deployments, why would you NOT be asking for this feature (not to mention the non-functional Approve/Broken buttons, but that's on another thread)? The current workflow is restrictive and frankly, not conducive for a Continuous Delivery process.

No luck thus far

I also require this feature; there doesn't even seem to be a workaround to this. We have Bamboo configured to create releases automatically after successful builds (using triggered deployments), and for builds on a branch we have no choice - you get the Bamboo versioning scheme.

If I were manually creating releases I could ignore the defaults and set the version myself. With automatic releases you don't have this opportunity.

There isn't even a REST API for creating releases.

I would second the request for this functionality. We use both feature *and* release branches in our GIT repository and we regularly need to release from one of the release branches. This defaulting of the release version is a large pain-in-the-neck.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events