Do not run Change Detection after customized run

Summary

If a Trigger is enabled, Change Detection runs after a build and tries to trigger a new build with any changes (BAM-18497). With customized builds (Run >> Run Customized), users have the option to run off of custom commit hashes, which may be on different branches. In these cases, Bamboo will not be able to download the changes and run the build.

Steps to Reproduce

1. Add a branch more_tests to a build
2. Configure a variable for the branch name (BRANCH_NAME)
3. Add a trigger on the repository
4. Do not merge more_tests to master
5. Run a custom build using the more_tests branch

Expected Results

Build runs as expected

Actual Results

• A build ran as expected using the latest changeset on more_tests; but
• Immediately after the build, change detection finds the delta between the revision used in the custom build and the latest revision on the master branch and triggers a new build

The following appears in the Commits tab:

[unknown]
Bamboo was unable to extract changes between revision <more_tests_commit_hash> and <master_commit_hash>.

Workaround

Remove any Triggers from the build