Use MSBuildCache build with Arcade fallback#10196
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: bec4a34f-864a-4726-9721-65deecab2682
There was a problem hiding this comment.
Pull request overview
Uses MSBuildCache outputs directly in Windows CI, with Arcade fallback behavior and documentation.
Changes:
- Align cache seed and consumer properties.
- Track cache success and clean failed outputs.
- Skip Arcade builds after cache success.
Show a summary per file
| File | Description |
|---|---|
azure-pipelines.yml |
Implements cached-build reuse and fallback logic. |
docs/dev-guide.md |
Documents cache behavior and local validation. |
Review details
Comments suppressed due to low confidence (1)
azure-pipelines.yml:425
- Skipping
CIBuild.cmdalso skips the repository bootstrap that installs the WASI workloads.build.ps1:105-107callseng/restore-toolset.ps1, but the directmsbuild.ps1path does not; the newly added-prepareMachineonly stops build processes on exit (tools.ps1:756-759). The Debug acceptance suite has always-ondotnet build -r wasi-wasmtests that assert exit code 0, so cache-success jobs will hit NETSDK1147 on clean agents. Run the custom toolset/workload bootstrap independently before tests rather than relying on the skipped Arcade build.
name: Build
displayName: Build
condition: and(succeeded(), ne(variables['MSBuildCacheBuildSucceeded'], 'true'))
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Medium
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: bec4a34f-864a-4726-9721-65deecab2682
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: bec4a34f-864a-4726-9721-65deecab2682
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: bec4a34f-864a-4726-9721-65deecab2682
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: bec4a34f-864a-4726-9721-65deecab2682
Build failure analysisAffected legs: Windows Release, Windows Debug Root cause
The contract test project ( FixAdd <TerminalReporterContractSource Include="$(_TerminalContractPlatform)\OutputDevice\SlowTestThresholdState.cs" />
<TerminalReporterContractSource Include="$(_TerminalContractPlatform)\OutputDevice\TargetFrameworkParser.cs" />This entry is shown in the PR diff as an intended change to
|
Summary
Upstream tracking
Validation
azure-pipelines.ymlsuccessfully