Summary

The 'Remote Trigger' in Bamboo is causing only main plans to be triggered, even though commits are made to branches associated to branch plans within that main plan.

Example:

I have the following test project setup:

Main plan with trigger "Repository triggers the build then changes are commited" and selected repository with branch "develop".

Branch plan with trigger "Repository triggers the build then changes are commited" and selected repository with branch "master".

For both repositories selected Bitbucket. (See screenshot for what I mean by that. I will test with Git later).

Now when I commit changes to master brach main plan gets triggered instead of Master branch plan. I expect Master branch plan to be triggered.

New commit to develop branch will trigger main branch plan as expected.

It works well if "Pull the repository for changes" selected.

Steps to Reproduce

1. Create a repository in BitBucket (and possibly other repositories) with the main and another branch, say test branch.
2. Create a plan in Bamboo associated with the main branch and a branch plan within it associated with the 'test' branch
3. Add repository to the plan
4. Create a 'Remote Trigger' in Bamboo to the repository and a service in Bitbucket, as described here, so BitBucket triggers the build immediately after commit
5. Commit to the 'test' branch

Expected Results

1. A build in the branch plan is triggered, as this is the one associated with the 'test' branch

Actual Results

1. The main branch is triggered

Workaround

1. Use repository polling instead