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?
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).
Earlier this year we made the difficult decision to discontinue our team messaging tools, Stride and Hipchat. The end of life date for Stride and Hipchat Cloud is quickly approaching - February 15, 2...
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!
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