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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.