Why does merge to master(default) triggers bamboo build plan for all other branches?

[Rachana B]

Background:

The existing Build Plan which was set up as 'Plan Branch' was migrated to be configured through Bamboo Specs where Linked Repository was done with a master branch (default). 

Problem:

When I merge to master, the build plan for all the branches gets triggered. Whereas this does not happen when feature branches merged with each other or with develop.

Does the Linked Repository have something to do with this? Or there is some linking/another enabled setting that can lead to trigger all branches?

[Robert C]

Same problem here, did you find a fix for this? Thanks

[Jörg Herzinger]

We have the same problem. It happens for all our pipelines defined by YAML specs, while the older Java spec pipelines work as intended. Even on Bamboo 9 this happens.

[Koen Mestdagh]

Hi @Rachana B 

Just to mention I have something which seems the same problem.

This only exists for one of our repositories.

After every merge to master, all branches of this repository are being built.

Regards

Koen