[57514396] Use the central TSA area path in Foundation native builds - #6681
Open
v-goradojcic wants to merge 1 commit into
Open
Conversation
|
Azure Pipelines: 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
v-goradojcic please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
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
Updates the Foundation native build paths to materialize the OneBranch root TSA configuration from the central WinAppSDK-core area path defined in WindowsAppSDKConfig.
Covered paths:
Dependency
The shared templates from WindowsAppSDKConfig PR 16332578 are merged and available on
WindowsAppSDKConfig/main:https://dev.azure.com/microsoft/ProjectReunion/_git/WindowsAppSDKConfig/pullrequest/16332578
Related OS/WinAppSDK consumer PR:
https://dev.azure.com/microsoft/OS/_git/WinAppSDK/pullrequest/16332587
Validation
Foundation PR builds 154413261 and 154428600 succeeded on the PR merge ref.
Validated:
.config/tsaoptions.jsoncontains the expected central area path.VSIX and Installer use the same shared materialization template, but their build phases are skipped in normal Foundation PR validation when
LatestOfficialBuildIDis not available.Remaining follow-up
The Foundation root
.config/tsaoptions.jsonintentionally retains the textual area path because the remaining non-native self-checkout jobs that can run TSA source scanners have not yet been migrated to the shared materialization step.Bug 57514396 should remain active until that remaining surface and the required branch ports are completed.
The numeric
AreaPathIdused by ComplianceValidationTask is outside the scope of this PR.AB#57514396