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?
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.
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.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs