We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
Managing the priority of pipelines runs pressing "run next" for each and every run is cumbersome.
As Azure DevOps is not supporting priortizing builds on a build config level (see https://developercommunity.visualstudio.com/t/ability-to-set-build-priority/365507), a workaround could be to manage the priority of pipeline runs after they were queued using this CLI.
Describe the solution you'd like
az pipelines run-next {run-id}
Best would be to just modify a build config. But if this is not possible, we should expose the "run next" feature through this CLI
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
Managing the priority of pipelines runs pressing "run next" for each and every run is cumbersome.
As Azure DevOps is not supporting priortizing builds on a build config level (see https://developercommunity.visualstudio.com/t/ability-to-set-build-priority/365507), a workaround could be to manage the priority of pipeline runs after they were queued using this CLI.
Describe the solution you'd like
az pipelines run-next {run-id}
Best would be to just modify a build config. But if this is not possible, we should expose the "run next" feature through this CLI
The text was updated successfully, but these errors were encountered: