Move official build pipeline to OneBranch #8319
Merged
Conversation
This file contains 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
microsoft-github-policy-service
bot
added
the
needs-triage
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
bkudiess
approved these changes
Mar 24, 2023
bkudiess
pushed a commit
that referenced
this pull request
Mar 24, 2023
bkudiess
pushed a commit
that referenced
this pull request
Apr 7, 2023
kmahone
added a commit
that referenced
this pull request
May 10, 2023
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.
For the official release builds we are moving the build Pipeline to OneBranch.
In this PR:
Added two new Pipelines, WinUI-OB-Official and WinUI-Official-Validation.
WinUI-OB-Official is the OneBranch pipeline that we use to build the product. WinUI-Official-Validation is a pipeline that takes the output of the former pipeline and runs tests on it. Our tests don't work in OneBranch so this is the way we need to do things.
A couple of changes required to support this:
Moved the build to VS 2022 and latest msvc build tools
This required a few minor fixes to the product code due to the updated compiler.
Source Indexing Use pdbstr/srctool from nuget instead of SDK
The OneBranch machines did not have these tools installed, so we consume them from nupkg instead.
Stop Building Microsoft.Experimental.UI.Xaml proj and nupkg
These are not being actively worked on so it is unnecessary to continue building. The code is still there if we decide to start using it again.
Minor refactoring of yml templates
Disabled VerifyUseCompactResourcesAPI and MetadataProviderTests.CanLoadXamlFragments when built with MUXFinalRelease
Previously we did not usually run the main test pass on MUXFinalRelease bits. But with the new workflow we do. These tests were failing in that config