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]

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 way...am I wrong?

[Marcin Gardias]

That options is coming in Bamboo 6.1

[Adam Sir]

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

[Marcin Gardias]

Yes, it has: https://confluence.atlassian.com/bamboo/naming-versions-for-deployment-releases-361726798.html

[carlos]

+1

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.

[Steve]

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

[Clayton Dukes]

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

[Ron Chan]

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 https://jira.atlassian.com/browse/BAM-14422.

[Mark Brodziak]

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.

[Iain Wilson]

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.