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?
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot