Unexpected Deployments Triggered - Want "master" Only Edited


Deployment process triggered by builds on branches other than master


We have a deployment process that is triggered by successful builds of the master branch. The deployment itself moves generated artifact to a remote server.

I recently started running "customized" builds of a non-master branch to generate artifacts I could manually download and test.  

I was surprised to see that the deployment process was triggered by these builds and moving the artifact to our remote server.


This is the deployment trigger. It looks to me like it should only activate on builds of master branch.


I create a build from some other branch of the build plan by

1. Click "Run > Run customised"


2. Enter desired branch and click "Run"



Am I missing a setting? Is there an alternate way I should be generating builds from arbitrary non-master branches?


1 answer

1 vote

Hi William,

This is working as designed.  Any successful build on that plan (branch or otherwise) will trigger the master deployment.



And to prevent that? To limit deployments to "master" branch builds only?

Hi William,

There is a feature request (Suggestion) that you can find at BAM-18793.  Please vote on that issue so we can get this behavior in front of the developers so we can see a change in Bamboo.



Thanks Branden.

To my reading, that suggestion implies that it is possible to do what I'm asking.

user will need to manually configure a deployment project to run on successful completion of a particular branch plan.

It sounds like I could configure the deployment to trigger on "master" only (a particular branch).

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
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,801 views 0 6
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