I have a plan that blocks a stage with status "Job has not yet been queued. Waiting for prior stages to complete." and yet the prior stages report status completed and at least 9 agents are available that can build the stage currently waiting.
This also affects a clone of the plan.
How can one go about troubleshooting what the issue is and resolving it?
I did check that before posting and, yes, multiple agents were online and able to run the job.
I subsequently discovered the issue:
The Job contained a disabled Task of type Artifact Download. The Artifact Download task had been created with a reference to a Plan that had subsequently been deleted from the system. Even though the Task was disabled, the system evidently blocked the Job from being scheduled because the referenced Artifacts were not available. After removing (deleting) the Task from the Job, the system now schedules the Job.
There are a few things that could have made this easier to understand:
In any event, I have figured it out and I appreciate your response.
... and 2018
No disabled tasks in either Stage1 or Stage2. All Stage2 artefact download tasks pull valid and non-zero shared artefacts.
Solution: I had changed the built artefacts in Stage1, and reflected the changes in the artefact downloads of Stage2 - but still Stage2 was not starting. The solution was to set all tasks download *ALL* artefacts, run a build, then reset it to pull only the new artefacts and success.
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
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