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

Nikolaos Rafail Papadakis

Hello,

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?

Daniel Santos_157bm4

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!