nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why do plans with Git Stash trigger get stuck on "checking out source code" status?

Kathy Warner

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?

Accepted answers

Marcin Gardias

Hi,

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:

Bamboo - Stash communication is down. If Bamboo detects that no events are coming from Stash it will automatically fall back on git polling.
Your plan contains repositories that are not served by Stash. Bamboo will do polling for them.

All comments

ThiagoBomfim

Hi Kathy,

Maybe you've multiple triggers configured on your build plans? I would focus on specially Polling.

Please refer to:

Triggering builds

Best,
Thiago

Kathy Warner

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?

Kathy Warner

Is there anything else I should be checking for?

Marcin Gardias

Hi,

Bamboo - Stash communication is down. If Bamboo detects that no events are coming from Stash it will automatically fall back on git polling.
Your plan contains repositories that are not served by Stash. Bamboo will do polling for them.