Skip to content

Fix template path in quarantine pipeline - #14937

Merged
AR-May merged 2 commits into
dotnet:mainfrom
AR-May:ar-may-fix-quarantine-template-path
Sep 7, 2026
Merged

Fix template path in quarantine pipeline#14937
AR-May merged 2 commits into
dotnet:mainfrom
AR-May:ar-may-fix-quarantine-template-path

Conversation

@AR-May

@AR-May AR-May commented Sep 4, 2026

Copy link
Copy Markdown
Member

The quarantine pipeline has not run since #14371 (~50 days!). It fails
while parsing YAML.

Cause: template: paths resolve relative to the file that contains them.
quarantine.yml is already in azure-pipelines/, so the extra prefix pointed to
a folder that does not exist.

Template paths resolve relative to the referencing file. quarantine.yml
is already inside azure-pipelines/, so the azure-pipelines/ prefix
resolved to azure-pipelines/azure-pipelines/ and the pipeline failed at
YAML compile time on every run since dotnet#14371.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@AR-May
AR-May marked this pull request as ready for review September 4, 2026 12:27
@AR-May
AR-May requested review from VolPlita and a lite review from Copilot September 4, 2026 12:27
@AR-May
AR-May enabled auto-merge (squash) September 4, 2026 12:29

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change is a straightforward correction of YAML template paths and appears consistent across all affected jobs with no functional risk beyond restoring the pipeline parsing.

Pull request overview

Fixes YAML template includes in the Azure DevOps quarantine pipeline by updating template: paths to be relative to azure-pipelines/quarantine.yml, restoring the pipeline’s ability to parse and run.

Changes:

  • Update the check-documentation-only-change.yml template reference in each quarantine job (Windows/Linux/macOS) to use a relative path.
File summaries
File Description
azure-pipelines/quarantine.yml Fix template include paths so YAML parsing succeeds and the quarantine pipeline can run again.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

@VolPlita

VolPlita commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

pipelines still fail, check-documentation-only-change.yml runs git diff ... HEAD~1, while the jobs use a shallow checkout without HEAD~1, so build never executes and artifacts are missing.

Comment thread azure-pipelines/quarantine.yml
The quarantine definition fetches with depth 1, but
check-documentation-only-change.yml runs `git diff HEAD HEAD~1`, which fails
with "unknown revision" because the parent commit was never fetched. The step
then fails the job before the build runs. msbuild-pr is unaffected because its
definition sets fetchDepth 0.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 0518e79a-a652-4869-aa2e-5dc82c738c0b
@AR-May
AR-May requested a review from VolPlita September 4, 2026 13:37
@AR-May

AR-May commented Sep 4, 2026

Copy link
Copy Markdown
Member Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).

@AR-May
AR-May merged commit 594deea into dotnet:main Sep 7, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants