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

Having problems with getting triggers for multiple repositories to work

We are using Bamboo Server version 6.6.3 build 60607 and I am having issues getting triggers to work.  Our project has many repositories and I am trying to create a single plan utilizing branch plans that will trigger a build if there is a change in any of the configured repositories.  

For my plan I have 10 "linked" repositories configured under the Repositories tab.  Under the Triggers tab I have selected "Bitbucket Server repository triggered" as we are using Bitbucket for our repository management.  Under the trigger I have selected repositories 3-9 as these are the only ones I want to trigger on.  Under the Branches tab I have chosen "When new branch in repository is created" so I can test just by creating branches in the various repositories.  Once working I plan to change this to "When pull request is created".

What I am seeing is that only branch plans are created when I create a branch in the 1st repository in the list.  As I stated earlier this is not one of the triggered repositories.

I'm trying to figure out

  1. Why is this the only branch plan being created?
  2. Why is this being created at all as it is not selected in trigger?

Any help getting this resolved will be greatly appreciated.  

1 answer

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 09, 2019

Hope it helps :)

You can vote

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events