Parent build plan triggers all child plan branches

[Stian Storrvik]

In my setup, I have project A that is a parent to project B, set up with Maven Dependencies Processor. When I trigger a build on project A, project B is built. All is fine. The same thing goes for any branch on project A. When project A branch A is built, project B branch A is also built.

However, if I trigger a project A master build, all of the branches on project B is built. Is there any way to avoid this?

I see absolutely no reason why a root build should trigger branch builds.

Edit: Bamboo is running on Bamboo 5.11.3 build 51118

Edit2: I've also set up an artifact download from project A when building project B. When I trigger project A master, project B branch A will fetch it's artifact from project A, branch A, which is the correct artifact. This indicates that there is some sort of path resolve that works when going from branch to branch, but not from nothing to branch.

Could it be that the matching pattern for branches is:

project - branch

and when the name is just project, branch gets replaced by * ?

okay, so I did some more digging:

given branches:

master (no extension)
branch1
branch1_alternate

I observe this behaviour: 

change in PARENT
triggers CHILD
and CHILD - BRANCH1
and CHILD - BRANCH1_ALTERNATE

change in PARENT - BRANCH1
triggers CHILD - BRANCH1
and CHILD - BRANCH1_ALTERNATE 

so it seems there is some wildcard matching here that probably shouldn't accept anything other than precise matches... 

[Stian Storrvik]

It seems this is a possible bug, so I'll leave this up for about a day, and if I don't get any answers, I'll create a support ticket.