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; } } }

Bamboo build is not queued, waiting for not existing stages

Sebastian Gingter

Hi, I'm evaluating Bamboo and it makes me some troubles: Builds are not starting and seem to be waiting forever.

Some Info:

I configured two local agents, both are capable of running the build.
The plan has a single stage "Build" with two tasks: Checkout and call msbuild with my solution file.

When I manually select 'Run' it is queued and 'waiting to be build' forever. When clicking onto it, and selecting the only stage with the hourglass besides it from the sidebar, it tells me this status:

Status: Job has not yet been queued. Waiting for prior stages to complete.

I am totally lost now. How can I start the build? There are no prior stages that could be completed, because the checkout and build is the only one.

Accepted answers

All comments

PiotrA

Hello Sebastian,

Can you share a screenshot of your plan's configuration page(s) ? I can't find anything wrong in your description, so probably the devil is in the details... Also, is there something unexpected in the atlassian-bamboo.log file (you should have it somewhere in your BAMBOO/logs directory)? Maybe you should consider raising an issue on https://support.atlassian.com - I reckon Atlassian support engineers are helpful during evaluations of our products (including Bamboo).

regards,

Przemek Bruski

Status: Job has not yet been queued. Waiting for prior stages to complete.

I think this is only a display issue, so don't worry about it for now.

Could you check Agent Matrix (in Administration) to see if your agents can build your plan?

Sebastian Gingter

It's not a display issues. Both configured agents are capable of running the build, and both are idle.

Now, this morning the build was executed. It ran about 3 hours after I clicked 'run' on the UI. Is it normal that I trigger a build and wait hours long with both agents idle to have the build start?

PiotrA

No, it's not normal.

Unless - for example - Bamboo is doing initial clone of laaarge remote repository... hm... what kind of repository are you using? Could it be an issue, that you're using large (gigabytes) Git or Hg repository?

Sebastian Gingter

I'm just evaluating the whole setup, so I use a private Bitbucket Git repo with two commits in it, the whole repo size under 50 kilobytes. I'm pretty sure that this is not the issue ;-)

Interestingly, right now the builds are pretty instant. But there are no log entries showing why the previous builds were delayed so extremely.

Anton Gorodishenin

Hello. I have similar problem. I run manual build and it hang without errors in "system errors" and logs. Executing first step of build not started.

I just connect to server by ssh and found processes, which recieve changes from github. I execute "kill -9" for this processes and restart build. After this build successfully started and executed without problems.