Skip to content

[57514396] Use the central TSA area path in Foundation native builds - #6719

Open
v-goradojcic wants to merge 4 commits into
mainfrom
user/v-goradojcic/57514396-centralize-tsa-area-path
Open

[57514396] Use the central TSA area path in Foundation native builds#6719
v-goradojcic wants to merge 4 commits into
mainfrom
user/v-goradojcic/57514396-centralize-tsa-area-path

Conversation

@v-goradojcic

Copy link
Copy Markdown
Collaborator

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:

  • BuildFoundation
  • AnyCPU
  • MRT
  • VSIX
  • Installer

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:

  • Materialization succeeded in BuildFoundation (x64/x86/arm64), AnyCPU, and MRT.
  • Generated root .config/tsaoptions.json contains the expected central area path.
  • No unresolved variables or placeholder area paths were present.
  • Existing TSA configuration fields were preserved.
  • OneBranch TSAOptions successfully validated the generated configuration.

VSIX and Installer use the same shared materialization template, but their build phases are skipped in normal Foundation PR validation when LatestOfficialBuildID is not available.

Remaining follow-up

The Foundation root .config/tsaoptions.json intentionally 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 AreaPathId used by ComplianceValidationTask is outside the scope of this PR.

AB#57514396

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@v-goradojcic

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

@v-goradojcic

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

@kythant

Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants