{CI} Add Azure Pipeline to trigger reference docs CI#33643
Merged
wangzelin007 merged 2 commits intoJun 25, 2026
Merged
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @wangzelin007, |
️✔️AzureCLI-BreakingChangeTest
|
microsoft-github-policy-service
Bot
requested review from
Pan-Qi,
jsntcy and
yonzhan
microsoft-github-policy-service
Bot
added
Auto-Assign
Collaborator
|
CI |
wangzelin007
force-pushed
the
migrate-trigger-reference-docs-ci-to-ado
branch
4 times, most recently
from
2561d2c to
fb69a2d
Compare
Add .azure-pipelines/trigger-reference-docs-ci.yml, an internal Azure Pipeline that queues the docs reference CI pipeline on release, replacing the GitHub Action's FIC-based login with an Azure DevOps service connection. The existing GitHub Action is kept for now as a safety net.
wangzelin007
force-pushed
the
migrate-trigger-reference-docs-ci-to-ado
branch
from
fb69a2d to
e232d8e
Compare
xmdanni
reviewed
Jun 25, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an internal Azure Pipelines definition to trigger the Microsoft Learn reference docs CI pipeline on Azure CLI release branch updates, replacing the retiring GitHub Action–based federated auth with an Azure DevOps service connection (WIF) approach.
Changes:
- Introduces
.azure-pipelines/trigger-reference-docs-ci.ymlthat triggers onrelease,release-lts-*, andtest-release-*. - Queues the appropriate downstream docs reference pipeline (LTS vs latest) via
az pipelines build queue, passing branch and provenance variables.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
xmdanni
approved these changes
Jun 25, 2026
naga-nandyala
approved these changes
Jun 25, 2026
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.
What
Adds
.azure-pipelines/trigger-reference-docs-ci.yml, an internal Azure Pipeline that queues the Microsoft Learn docs reference CI pipeline when Azure CLI releases — the same job the existing GitHub Action.github/workflows/TriggerReferenceDocsCI.ymldoes today, but authenticating with an Azure DevOps service connection (Workload Identity Federation) instead of a federated GitHub login.Why
The federated credential the GitHub Action relies on is being retired, so the trigger logic is moving into an internal Azure Pipeline.
How it works
release,release-lts-*, andtest-release-*(the last is for the team to test in isolation). A jobconditionfurther restricts execution to those branches, so a stray manual run on any other branch is skipped.Build.SourceBranchName— no manual parameter to fill.release-lts-*→ the LTS docs pipeline; everything else (release,test-release-*) → the normal (latest) docs pipeline.az pipelines build queue, passing the branch through to the downstream pipeline.The GitHub Action is intentionally kept
TriggerReferenceDocsCI.ymlstays in place as a safety net and will be disabled once the new pipeline is validated. Thetrigger:here only takes effect once the pipeline is registered in ADO, so merging this file is inert until then.Follow-ups before it goes live
ADO_DocsReference_ServiceConnection.ADO_DocsReference_Organization,ADO_DocsReference_Project,ADO_DocsReference_Latest_Pipeline_ID,ADO_DocsReference_LTS_Pipeline_IDvia a variable group (uncomment the- group:line) or pipeline variables.azure-devopsCLI extension is available on the agent pool.test-release-*branch, then disable the GitHub Action.