Repository navigation
azure-pipelines: Stage 2 deprecation of old azure-pipelines templates - #2409
Merged
Brandon Waterloo [MSFT] (bwateratmsft) merged 3 commits intoOct 6, 2026
Merged
Brandon Waterloo [MSFT] (bwateratmsft) merged 3 commits into
Brandon Waterloo [MSFT] (bwateratmsft) merged 3 commits into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Brandon Waterloo [MSFT] (bwateratmsft)
requested a review
from a team
as a code owner
October 6, 2026 16:17
Brandon Waterloo [MSFT] (bwateratmsft)
changed the title
Brandon Waterloo [MSFT] (bwateratmsft)
changed the title
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot started reviewing on behalf of
Brandon Waterloo [MSFT] (bwateratmsft)
October 6, 2026 16:23
View session
Patrick Verbrugge (patverb)
approved these changes
Oct 6, 2026
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The three legacy entry points consistently implement the documented non-blocking error behavior.
Review effort: Balanced
Findings: None
What changed in this PR
Escalates legacy Azure pipeline template deprecation notices to non-blocking errors while preserving subsequent build and release execution.
Changes:
- Emit deprecation errors and exit each notice step with failure.
- Use
continueOnErrorto allow later pipeline steps to run. - Document stage 2 behavior and migration guidance.
| File | Description |
|---|---|
azure-pipelines/release-extension.yml |
Escalates the extension release notice. |
azure-pipelines/README.md |
Documents stage 2 deprecation behavior. |
azure-pipelines/1esstages.yml |
Escalates the build-stage notice. |
azure-pipelines/1es-release-npm.yml |
Escalates the npm release notice. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Brandon Waterloo [MSFT] (bwateratmsft)
deleted the
bwateratmsft-deprecate-old-pipelines
branch
October 6, 2026 16:25
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
azure-pipelines/deprecation notices from warnings to Azure DevOps errors.exit 1, but setcontinueOnError: trueso subsequent build and release steps still run and pipelines partially succeed.azdo-pipelines/templates are unchanged.Part of #2177.
Validation
git -c core.whitespace=cr-at-eol diff --check: passed.