While we are working with Azure DevOps pipelines for build and deployment purpose, we use several private and hosted agents. However, sometimes there are more CI and PR builds in the queues due to limited number of parallel job availability. While we do daily tasks, there can be situations where we need to release a bug fix quickly but pipelines have long queues. At that type of situation, team has to wait prior until all the builds on the queue get completed. This blog explains the feature available in Azure DevOps as a solution to this issue.
Go to the build logs of the build pipeline which need to be started next. In the logs you would be able to see the position of the current build . As the following image the selected build is 4 th in the queue. We can click on the "Run next" to queue this build next as priority.
Once click on the "Run next", you would be able to see the current position in the queue value has changed to 1 as follows.
Go to pipelines and you would be see that selected build started before the other builds in the queue.
This post shared a small but very useful feature available in Azure DevOps. This helps you to trigger important builds without staying in the build queues for long time.
No comments:
Post a Comment