We have quite a number of plans in our Bamboo installation, all of which are set up to be triggered via Stash. For some reason, however, all of our plans at any given time (not at once) will change its status to "checking out source code" without any code changes being made to Stash.
Why is this?
The answer is: Stash trigger is not only passively waiting for events from Stash, but it also has a polling job that runs periodically and checks for changes if needed. There are 2 cases when it's needed:
I've checked this setting on all of our build plans and can confirm that each one is using "Stash repository triggered", which is why I'm scratching my head. The way I understand this trigger is that Bamboo should have no knowledge of when it's supposed to fire off a build plan. Instead, the onus is put on Stash to fire off an event telling Bamboo when it's time to build. Is that correct?
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
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