Cleanup of ADO pipeline YAML files #615
Merged
Conversation
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
walbourn
commented
May 20, 2025
walbourn
commented
May 20, 2025
walbourn
commented
May 20, 2025
scm-xbox
approved these changes
May 23, 2025
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.
This PR adds the use of strategy and templates to the existing ADO pipelines.
For the basic builds using Visual Studio MSBuild with minimal job setup, I made use of
strategymatrixto simplify the pipelines for GitHub, GitHub-Dev17, GitHub-Test, and GitHub-Dev17.For the Windows SDK and GDK NuGet pipelines which have substantial package sizes as part of job setup, I made use of
templatefor SDK-release, SDK-prerelease, GDK, and GDK-Dev17 pipelines to share implementation.