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

https://bamboo.companyname.com/api/rest/updateAndBuild.action?buildKey=${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  bamboo.companyname.com 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 Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

45 views 0 2
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you