Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to properly set branch plan trigger for Pull Request?

I have a Project on Bamboo, let's call it A. Within A, I have 2 Build plans:

  • Master Build Plan
  • PR Build Plan

Both build plans have the same repository and with master branch being the default branch.

Master Build Plan plan branch option is set to Manually so it never creates other branch plans and the trigger is set to repository change.

PR Build Plan plan branch option is set to 'When pull request is created', so it only create branches related to PRs.

If on PR Build Plan, I disable the repository trigger, if I update my PR, it doesn't trigger a new build. If I enable it, it triggers when PR is updated but after merging the PR into master branch, PR Build Plan runs on the master branch, that is the default branch of the repository, which is not desirable.

Is there a way to keep the PR Build Plan triggering when the PR is updated without running for master branch when master gets updated?


1 answer

1 accepted

1 vote
Answer accepted
Jeremy Owen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 25, 2018

Hey Luiz,

Try disabling the "master" of your PR Build Plan from Plan Configuration >> Actions >> Disable Plan.

Branch / Pull Request detection and triggering still works even if the master plan configuration is disabled, but master won't trigger. :)

Hope this helps.



Thank you.

This option should be set by default when 'create plan branch' is set to 'When pull request is created', though.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events