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
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
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?
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.
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.