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
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?
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?
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...
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