nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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 Chan2

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?

Accepted answers

All comments

Iain Wilson3

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.

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.

Ron Chan2

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.

Clayton Dukes

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

Steve91

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

carlos27

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.

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

bamboo-administration