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!


Bamboo skips commits for building

Our Bamboo plan has a configuration to trigger on every commit (Bitbucket Server repository triggered).

Sadly, some commits doesn't trigger the Bamboo plan to run.

You can see that there are two PullRequest merges which result in one build. But they should result in two builds, one for each.bamboo-bug.png

Does someone know why this could happen or how it could be fixed?

1 answer

0 votes
Jeyanthan I
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 28, 2020

Hi @danieldaeschle ,

I can think of 2 possibilities:

  • You might have quiet period configured in this linked repository. This is the time Bamboo should wait for any new change before initiating a build. If these 2 pull requests have happened consequtively, these both could have triggered just one build.
  • You have configured Exclude changesets under this linked repository definition. If a regular expression in this field matches the commit messages, it will be excluded from triggering a build.

There can be other factors like network problem influencing this. You may get more details from your atlassian-bamboo.log.


Both are deactivated.

Any other suggestion?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events