Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

191 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you