Bamboo builds not getting triggered with merge commits Edited

We have a Bamboo build plan set up to poll a list of repositories once a day. If a change is found in the 'develop' branch, a build should ge triggered.

However, we are finding that these builds almost never get triggered, but sometimes they are.

After investigating the issue further, it seems that Bamboo is triggering the build if we have committed a change directly into the 'develop' merge.

However, if we only add a merge commit into 'develop', no build is triggered.

Is there anything that we can do to trigger the build in Bamboo if a merge commit is found?

1 answer

0 vote

At the Bamboo repository level, have you excluded merge commits using 'Exclude changesets'?

Or do you have a 'quite period' that is simply making the build wait?

Hello,

No, the checkbox 'Enable quiet period' is NOT checked.

Also, the field 'Include / exclude files' is set to the default value of 'None'.

If you require anything else please let me know.

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
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,096 views 0 5
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot