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.
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