Repository triggers the build when changes are committed

[lance_lyons]

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?

[Przemek Bruski]

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?

[lance_lyons]

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.