Question

Your team runs an Azure DevOps YAML pipeline that builds and tests a large .NET solution on Microsoft-hosted agents. The pipeline is triggered on every push to any feature branch, and you have observed that concurrent runs frequently queue for long periods, driving up parallel-job costs and delaying feedback. Management wants to reduce cost and queue time without abandoning per-branch validation. Which change should you implement first?

Accepted Answer

Add a batch: true setting on the CI trigger so pushes to the same branch are batched into a single run while a build is in progress

Answer

Increase the number of purchased Microsoft-hosted parallel jobs so every push starts immediately

Answer

Convert the pipeline to a classic release pipeline to avoid parallel-job consumption

Answer

Set a scheduled trigger that runs the pipeline once per hour instead of on push