-
Notifications
You must be signed in to change notification settings - Fork 5.3k
ci-analysis: Add Azure CLI guidance for AzDO pipeline investigation #124193
New issue
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
Conversation
- Add 'Deep Investigation with Azure CLI' section with auth checking - Add pipeline definition and build querying examples using az CLI - Add guidance to examine pipeline YAML in dotnet/dotnet - Prefer az CLI commands over manual REST API construction - Add tip #8 about verifying az auth before REST calls
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates the ci-analysis skill documentation to add guidance for using the Azure CLI (with the azure-devops extension) to investigate Azure DevOps pipelines and runs, reducing reliance on manual REST calls.
Changes:
- Adds a new “Deep Investigation with Azure CLI” section covering auth checks, pipeline/run queries, and artifact listing.
- Adds REST API fallback examples for build timeline querying and artifact ZIP downloads when CLI isn’t sufficient.
- Adds a new Tips item reminding investigators to verify
az account showbefore making REST calls.
Multiple agents running concurrently would stomp on each other's global az devops config. Pass org/project explicitly instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
Summary
Adds Azure CLI guidance to the ci-analysis skill for investigating AzDO pipelines directly, reducing reliance on manual REST API construction.
Changes
New section: "Deep Investigation with Azure CLI"
azis installed/authenticated, refresh PATH on Windows, checkazure-devopsextensionaz pipelines list,az pipelines show,az pipelines runs list/showaz pipelines runs artifact listeng/pipelines/; useaz pipelines showto find the YAML pathKey principle: prefer
azCLI over manual REST API construction--query(JMESPath) and-o tablereduce scripting overheadConcurrency safety: never use
az devops configure --defaults--organd-pexplicitlyTerminology fix: AAD access token, not PAT
New tip Darc removes the TEST_RESTORE_SOURCES_INSERTION_LINE placeholder line in NuGet.config. #8: verify
az account showbefore making REST calls