ci-analysis: Add Azure CLI guidance for AzDO pipeline investigation#124193
Merged
ci-analysis: Add Azure CLI guidance for AzDO pipeline investigation#124193
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
Contributor
There was a problem hiding this comment.
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.
steveisok
approved these changes
Feb 9, 2026
iremyux
pushed a commit
to iremyux/dotnet-runtime
that referenced
this pull request
Mar 2, 2026
…otnet#124193) ## 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"** - Auth checking: how to verify `az` is installed/authenticated, refresh PATH on Windows, check `azure-devops` extension - Pipeline querying: `az pipelines list`, `az pipelines show`, `az pipelines runs list/show` - Artifact listing: `az pipelines runs artifact list` - REST API fallback: only for build timelines and artifact downloads (no CLI equivalent) - Pipeline YAML: all arcade-based dotnet repos use `eng/pipelines/`; use `az pipelines show` to find the YAML path - **Key principle: prefer `az` CLI over manual REST API construction** - CLI handles auth, pagination, and output formatting automatically - `--query` (JMESPath) and `-o table` reduce scripting overhead - **Concurrency safety: never use `az devops configure --defaults`** - Global config causes conflicts when multiple agents run concurrently - Always pass `--org` and `-p` explicitly - **Terminology fix: AAD access token, not PAT** - **New tip dotnet#8**: verify `az account show` before making REST calls
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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