Jeff Patton
Reputation: 574
A release pipeline is queued with multiple agents idle
We have an issue where currently we have a single release running and one release queued. Normally this would be ok, but we run self-hosted agents and have currently 9 agents sitting idle to run the release. I keep seeing parallel jobs, but I don't know if that solves this, as this feels more like something that I have misconfigured.
Since this post we have purchased 10 parallel jobs for the self-hosted pool and still are seeing this issue.
Upvotes: 0
Views: 2419
Answers (1)
Felix
Reputation: 1152
In your current situation, we recommend you can try to check your Deployment queue settings, this setting is used to configure actions when multiple releases are queued for deployment. You can select the 'Unlimited':
Upvotes: 1
Related Questions
- How to set a Agent Queue in a Release definition using REST API?
- How to queue multiple runs of same azure pipeline on one agent
- Azure DevOps Release Pipeline Fails Every Time
- Azure Release Pipeline - How to Set Agent Pool
- Deployment Agent is single threaded but we need multiple?
- Are the agents released when the pipeline is waiting for approval?
- How to not queue new build if no available agents
- Azure: The agent has received a shutdown signal. This can happen when the agent service is stopped, or a manually started agent is canceled
- Release Agent Demands in VSTS
- Stalled Hosted Agent VSTS