Why only releases from your default branch make use of the release version naming scheme?

In our deployment projects we have setup a release naming scheme using variables: ${bamboo.lein.version}-${bamboo.buildNumber}


The ${bamboo.lein.release} variable is injected from version stored in leingen (clojure build tool) project.clj file in source repository.

This naming scheme works great from integration/master build plan.

However, when we deploy from a release plan branch the naming scheme is changed to <branchname>-<incremented number>. This is messing up our release version naming scheme.

Why only releases from your default branch make use of the release version naming scheme??

1 answer

0 votes

Good question...

I guess our idea was that people will typically deploy from single branch and we wanted release sequence to be easy to grasp. Since there seem to be significant demand to change it, we will reconsider this decision. I can't promise you any specific release number/date atm. though.

Please vote here: https://jira.atlassian.com/browse/BAM-14422

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,085 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot