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

Repository triggers the build when changes are committed

We are trying to setup remote triggers to trigger a build that will only build when there are repository changes.

To do that we are calling a restapi to trigger the build${project.buildKey}

we also have a trigger on the actual build set to "Repository triggers the build when changes are committed" and the ip address of set as the trigger IP.


What we are seeing is every repository change triggers the build like repository polling.

We are not doing repository polling.


What might be our issue here?

2 answers

It appears like what I said above is not completely accurate.    What we are actually seeing is when bamboo is recycled (service restarted)  the builds that are set as  "Repository triggers the build when changes are committed"  get triggered.

0 votes

That's expected behaviour post-restart. Bamboo does not know what calls it may have missed while it was down, so it checks all repositories for changes. But that should not trigger a build, unless there were changes in the repo. Is this what you're seeing?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Unable to add or edit Bitbucket Cloud repository in Bamboo

On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...

302 views 2 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