Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automatically create Deployment Plan per Branch (like branch build plans)

Our current workflow involves our devs creating feature branches for each new feature from JIRA.  When a change is committed, Bamboo creates a new branch build plan for the new branch.  This runs, tests and creates artifacts.  I need to be able to deploy these, but to create a deployment plan, I need to specify a branch... manually...

Ideally, when bamboo creates a branch build plan, I should be able to specify if I want a deployment plan for that branch.  

Is there a way to do this currently.  For front end developers, we want deploy to an nginx server which is configured to handle a domain from the master branch and subdomains from feature branches.

This part is all working.  It just doesn't trigger the deploy on successful build plan completion.  With the introduction of containerisation, it is possible to simultaneously deploy multiple branches which are uniquely referenceable.  Unfortunately, it appears that Bamboo does not agree, insisting that a single environment can only have a single branch deployed at any one time, and that all deployments should come from the deployment (master) branch.  This simply is not the case any more.

Am I missing something here, or is it just not possible.  I was lead to believe that the latest 6.1 upgrade would resolve this.  I have upgraded, and it appears to have broken a lot of existing deployments. 

1 answer

0 votes

Hi Chris,

This is currently not available but there are two Suggestions for this that you can vote on.  Once you do that you'll be notified of any updates/workarounds, etc.:

Please vote on the two issues to add impact so this feature can get more visibility and hopefully be added in the future.

Cheers,

Branden

This has been revisited again at our company.  We still need this functionality.  Do we have to revert back to Jenkins to get the ability to parameterise our deploys based off of the branch name.  

Another possible solution would involve plan continuation for specific branches only.  However, this does not seem possible as there is no conditional flow control.

@somethingblueit's 2.5 years later and this feature still hasn't been implemented? It's a pretty basic requirement for CI/CD.

@Graham Ballantyne IKR? I also tripped on this very stone. I am about to create a manual stage for my bamboo plan to achieve some half-assed deployment solution because of this limitation.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

986 views 4 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you