Skip to content

Correct Variable Template Reference in NonOfficial Pipeline Templates#27275

Draft
jshigetomi wants to merge 3 commits intoPowerShell:masterfrom
jshigetomi:nonOfficialPipelinesFix
Draft

Correct Variable Template Reference in NonOfficial Pipeline Templates#27275
jshigetomi wants to merge 3 commits intoPowerShell:masterfrom
jshigetomi:nonOfficialPipelinesFix

Conversation

@jshigetomi
Copy link
Copy Markdown
Collaborator

@jshigetomi jshigetomi commented Apr 15, 2026

PR Summary

This pull request updates documentation and several ADO pipeline YAML files to standardize the use of the .pipelines directory and corrects relative paths for template imports. The changes ensure consistency between documentation and implementation, and fix broken template references in NonOfficial pipeline YAML files.

Documentation updates:

  • Updated all references in .github/agents/SplitADOPipelines.agent.md from ./pipelines to .pipelines to match the actual directory structure and improve clarity in instructions. [1] [2] [3] [4] [5] [6]

Pipeline YAML fixes:

  • Corrected template paths in all NonOfficial pipeline YAML files under .pipelines/NonOfficial/ to use ../templates/ instead of ./pipelines/templates/, ensuring the templates are correctly referenced relative to their location. [1] [2] [3] [4] [5] [6] [7] [8] [9]

PR Context

NonOfficial pipelines will not run without this fix.

PR Checklist

@jshigetomi jshigetomi added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Apr 15, 2026
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines:
5 pipeline(s) require an authorized user to comment /azp run to run.

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines:
5 pipeline(s) require an authorized user to comment /azp run to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backport-7.4.x-Consider Backport-7.5.x-Consider Backport-7.6.x-Consider CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant