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

Plan Branches Build Not Always Triggered On Relative BitBucket's Repository Change


We have multiple Bamboo build plans with the same configuration both in Bamboo and in their relative BitBucket's repo, but we have observed that for some of them the build for their plan branches (default and non-default ones is not automatically triggered when code changes hit the relative repo's branch, despite having set up the needed trigger ("Bitbucket Server repository triggered") in the build plan for all of them.

We cannot identify why this keeps happening, since as already mentioned, configuration is the same for all these build plans (coming from bamboo specs project).

This causes significant problems, since we expect plan branches to auto build on BitBucket's branch's change and produce new artifacts with the expected updated content, and if this not happens we end up with outdated/wrong content being produced without being able to easily identify it, unless they are deployed (too late and too bad to happen).

Any ideas about why this keeps happening and what may be the root cause of this case?

1 answer

0 votes

Hi @Nikolaos Rafail Papadakis

Given the type of problem you are experiencing, we need private data to investigate it further. I opened a support ticket on your behalf to allow this investigation. You should be receiving an email from our support channel about this ticket soon.

Once the investigation is finished, please take some minutes to share what were your findings here. This will help other users that may lend on this thread.

Thank you!

I've updated the support ticket as requested and I'm now waiting for any feedback.

When we reach any conclusion/solution, I'll update this thread accordingly.


Kind Regards,


Like Daniel Santos likes this

Thank you very much! =]

Hi @Nikolaos Rafail Papadakis

Your prior message was somehow categorized as spam. It happened probably because the same message was posted in two different threads. I've cleaned all the attempts you did from our spam queue so it does not try to filter your next comments out =]

Message to foreign users 
If you are trying to find a conclusion for this thread, please check this other thread where Nikolaos shared his findings:

@Daniel Santos I've just added a similar comment, almost at the same time as yours. :)


Kind Regards,


Like Daniel Santos likes this

If you don't mind I can remove that one. =]


Yes, you can remove it if you want, no problem from my side.


Kind Regards,


Like Daniel Santos likes this

Done! =]

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events