Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Unexpected Deployments Triggered - Want "master" Only Edited

Problem: 

Deployment process triggered by builds on branches other than master

Background:

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.

Steps:

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

trigger-configuration.png

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

1. Click "Run > Run customised"

run-customized.png

2. Enter desired branch and click "Run"

run-constomized2.png

 

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.

Cheers,

Branden

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.

Cheers,

Branden

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
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

190 views 4 6
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