Common pitfalls
Understanding and proactively addressing certain common mistakes and issues in Azure Pipelines is essential. You can save valuable time and resources by learning how to recognize and resolve them promptly.
In the context of real-world projects, timely resolution is essential to prevent delays and costly setbacks, allowing you to maintain project momentum and focus your efforts on other critical aspects.
Let’s discuss the details of these common errors:
- Sometimes, you may start the run of a pipeline and see it is queued. This could be because there is no available agent on Microsoft-hosted or self-hosted agents, insufficient concurrency, or unmet demand for agents. You can see the error immediately after you see the status of the job in your pipeline, as shown in the following screenshot:
Figure 12.1 – A job queued due to unavailability of agents
This might be an indication that additional parallel jobs must...