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 Sign up to answer
Community showcase
Asked Dec 06, 2018 in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,670 views 22 17
View question

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