Reputation: 81
The error message that I receive is Error: The agent request is not running because all potential agents are running other requests. Current position in queue: 1
When I execute the build definition using Microsoft agent, it results in the error above. The build execution took days and it has been abounded. Can someone please help me to run out of this issue?
The scenario I tried with Microsoft agent "Azure pipelines":
Upvotes: 8
Views: 22972
Reputation: 926
In my case, the problem was caused by the pipeline defining Demands:
exists msbuild
exists visualstudio
There was only a Visual Studio Team Explorer installation on the machine where the pipeline agent was installed. The Pipeline agent had MSBuild listed in the Capabilities section, but VisualStudio was missing.
After installing the full version of Visual Studio and restarting the pipeline agent service, the Capabilities section for this agent showed VisualStudio in addition.
After that, the pipeline agent is already working and processing the pipeline tasks.
Upvotes: 0
Reputation: 30343
Please follow below steps to check the status of your self-hosted agents.
Navigate to azure devops Project settings-->Agent pools-->Select the agent pool where your self-hosted agent resides-->Go to Agents tab-->make sure the agent is online
If the agent is offline. Please go to the self-hosted agent installation folder and manually start the agent by runing run.cmd
file. If the agent cannot be started. Please reinstall your self-hosted agent.
If the agent is already online. That means there are not enough agents in the agent pool to run your pipelines. You need to create more self-hosted agents.
Note:
If you are using classic UI pipeline. You should know you can configure the agent selection in two places ie. Pipeline scope and Agent job scope
The agent configuration in Agent job scope will override the agent configuration in Pipeline scope.
If you want to use Microsoft agents. Please make sure you select the Microsoft agents in the Agent job scope.
Upvotes: 6