Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,467,417
Community Members
 
Community Events
177
Community Groups

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

Edited
Rachana B
Rachana B Feb 04, 2022

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?

Answer
Watch
Like Jörg Herzinger likes this
160 views

2 answers

0 votes
Jörg Herzinger
Jörg Herzinger Dec 07, 2022

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.

Reply
0 votes
Koen Mestdagh
Koen Mestdagh I'm New Here Aug 24, 2022

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

Reply

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS

Atlassian Community Events

See all events