Bamboo build plans with linked repositories(having Change detection options configured ) aren’t triggered occasionally for commits made on the Bitbucket Server/DC repository

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


Bamboo has a linked repository configured for a remote repository stored in Bitbucket Server/Datacenter. A Bamboo plan is configured with this linked repository to trigger builds on code commits. When a Pull request is created or a commit is pushed in the Bitbucket remote repository, occasionally builds are not triggered in Bamboo for that plan.


All supported versions of Bamboo and Bitbucket Server/DC.


Check the Bamboo server logs in <Bamboo-home>/logs/atlassian-bamboo.log file around the timestamp the commit is triggered in the Bitbucket repository.

If you see something like below for the commit id(check the commit id from the Bitbucket Server/DC under the repository > commits section) in Bamboo server logs: 

2023-01-12 12:48:47,446 INFO [10-BAM::PlanExec:pool-17-thread-4] [DefaultChangeDetectionManager] : Excluding changeset 'bfcd999524ca010595265c87181000f89326895' from change log.
2023-01-12 12:48:47,462 INFO [10-BAM::PlanExec:pool-17-thread-1] [DefaultChangeDetectionManager] : Excluding changeset 'bfcd999524ca010595265c87181000f89326895' from change log.

These log messages say that the changes are being excluded for this commit id.

Check if any configuration is defined for the issue repository under Bamboo Overview > Linked repositories >Select the  Repository > Change detection options > Exclude Changesets tab. See if any file patterns or regular expressions set to match the commit messages for changesets to exclude and not to start a build. If any defined, see if the configuration matches the commit messages of the changes which are omitted to start a build in Bamboo. If you find the match between them then the solution mentioned in this KB will apply to you.

For Example, see below the sample configuration for a Linked repository in Bamboo:

From the above "Change detection options" configuration defined, there are two rules for exclusion:

  • Any file with pattern .md will be ignored
  • Also there is a regular expression present in the exclusion for the commit messages, which will ignore the files if their commit message match this pattern ((.[integration])). 


Because of configuration defined for Change detection options under Linked repository in Bamboo, Changesets will be excluded for the commit messages which match the file pattern or regular expression set under Change detection options > Exclude changesets tab and will not start build for those commits.


Review the file patterns or regular expressions defined for Change detection options under Linked repository. Remove the Exclude Changeset rule defined for the linked repository or update the same so that the changes for commits are not excluded in Bamboo and will trigger a build for the commits made in Bitbucket repository.

Last modified on Mar 30, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.