[CI] Build broken on release/13.3 — 20260514.11

[joperezr]

🤖 This issue was filed automatically by a daily monitoring bot.

The most recent completed run of the internal microsoft-aspire pipeline on
elease/13.3 failed.

• Build: 20260514.11 (id: 2975293)
• Result: Failed
• Started: 2026-05-14T21:03:56Z · Finished: 2026-05-14T23:12:29Z
• Commit: b8df57a7ede1d52f500af3bb86e75a4c4bec5267
• Internal link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2975293

First-level analysis

All platform build jobs (win_x64, win_arm64, linux_x64, linux_arm64, linux_musl_x64, osx_x64, osx_arm64, Windows) completed without errors. The only jobs with actual errors are the two publishing stages — WinGet Manifest and Homebrew Cask — and both fail with the same root cause: an expected artifacts/log/Release directory does not exist on the agent (Error: Not found SourceFolder: artifacts/log/Release / Path does not exist: artifacts/log/Release), causing a downstream Bash exited with code '1'. Likely an artifact-staging or log-copy step before these publish jobs did not produce the expected directory in this configuration.

---

cc @radical @joperezr

[joperezr]

🤖 Aspire triage pass — 2026-05-15 00:38 UTC

Area: area-engineering-systems
Kind: test-failure (CI publish-stage failure on release/13.3)
Repro: yes-minimal — internal pipeline run referenced in issue body (build 20260514.11)
Affected version(s): release/13.3 branch (servicing)
Severity: S2 — release-branch publishing pipeline (WinGet Manifest, Homebrew Cask) broken; blocks shipping artifacts. Core build jobs all green.

Urgency: 🔴 servicing — recommend milestone 13.3.x
Reason: failure is on the release/13.3 shipping branch and prevents the WinGet/Homebrew publish stages from completing for in-market bits.

Suggested owner(s): @radical (score ~36), backup @mitchdenny (score ~3)
Evidence (computed from merged PRs labeled area-engineering-systems in the last 90 days; @-mentions inside the issue body were not used):

• @radical merged: Avoid empty test summary artifact URL #16478, Add LocalArchive + DotnetTool CLI install modes for E2E tests #16454, feat(ci): add test failure retry support to auto-rerun workflow #16446, Publish and sign CLI install scripts #15127, [CI] Fix randomly failing tests on azdo due to docker+testcontainers/ryuk issues #15111, Automatically rerun transient CI failures #15110, [CI] Update to newer linux image on internal pipeline #15055, Reduce the number of PR validation jobs #15031, Reduce PR validation time by decoupling CLI archive dependencies #15023, [release/13.2][CI] Use large runner for Aspire.Hosting.Tests #15016, Add 3rd-party signing entries for Sigstore, Tuf, and NSec.Cryptography #14915, [release/13.2][CI] Unified test splitting infrastructure for CI parallelization #14858, Improve fix-flaky-test skill and reproduce workflow #14710, [release/13.2] Add Homebrew and WinGet packaging for Aspire CLI #14690 in area-engineering-systems (last ~90d) — dominant recent contributor
• @mitchdenny merged Remove test-scenarios infrastructure #14639 in area-engineering-systems
• CODEOWNERS not consulted: issue body does not cite specific source paths (failure is in pipeline YAML / artifact-staging step)

Confidence: high
Needs human?: no

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.

[radical]

This is needed on the branch - #16865 .

[joperezr]

🤖 Daily monitor: build still failing.

• Build: 20260514.13 (id: 2975377) on release/13.3
• Result: Failed
• Commit: a4615e7c6def6cba4703cdbd84009cd3da9a261b
• Internal link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2975377

[joperezr]

This is needed on the branch - #16865 .

Can you please backport to release/13.3 in case we do another patch release?

[joperezr]

🤖 Daily monitor: build still failing.

• Build: 20260514.13 (id: 2975377) on release/13.3
• Result: Failed
• Commit: a4615e7c6def6cba4703cdbd84009cd3da9a261b
• Internal link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2975377

First-level analysis

Failing jobs: Homebrew Cask (macOS) and WinGet Manifest (Windows). Both are CLI-packaging jobs that expect a artifacts/log/Release directory which is not present. Homebrew Cask shows an upstream Bash exited with code '1' (likely the packaging/staging script) — the missing-folder errors and the 1ES PT non-production-output errors look like downstream symptoms of that. Likely category: artifact-staging / build-script failure in the CLI packaging stage.

[joperezr]

🤖 Daily monitor: build still failing.

• Build: 20260514.13 (id: 2975377) on release/13.3
• Result: Failed
• Commit: a4615e7c6def6cba4703cdbd84009cd3da9a261b
• Internal link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2975377

First-level analysis

Same failure as previously reported. Failing jobs are WinGet Manifest and Homebrew Cask — both CLI-packaging stages expect an artifacts/log/Release directory that is not present on the agent. Homebrew Cask additionally surfaces an upstream Bash exited with code '1' (the packaging/staging script), with the missing-folder and 1ES PT "non-production output" errors as downstream symptoms. All platform build jobs (win_x64, win_arm64, linux_x64, linux_arm64, linux_musl_x64, osx_x64, osx_arm64, Windows) are clean. No newer completed run has occurred for this branch since the previous daily check — likely category: artifact-staging in CLI packaging stage (release/13.3 still missing the fix from #16865).

[joperezr]

🤖 Daily monitor: build still failing.

• Build: 20260517.4 (id: 2977116) on refs/heads/release/13.3
• Result: Failed
• Commit: 202b001120d0c22459934a613ba64c9668ace395
• Internal link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2977116

First-level analysis

The Homebrew Cask and WinGet Manifest packaging jobs failed; all build jobs (win_x64, linux_x64, osx_arm64, Windows, etc.) and Publish Assets succeeded. Both packaging jobs fail on the same root cause: the expected source folder artifacts/log/Release is not present when they try to copy/upload it (Not found SourceFolder: …/artifacts/log/Release). The accompanying 1ES PT Error: non-production output criteria messages are downstream symptoms of the missing folder. Likely category: artifact-staging/wiring on the release/13.3 branch — earlier stages aren't producing the log/Release outputs that the Homebrew/WinGet jobs consume.

[joperezr]

🤖 Daily monitor: build still failing.

• Build: 20260518.8 (id: 2978146) on release/13.3
• Result: Failed
• Commit: 75080796af797483231a9da2d1642b5130617565
• Internal link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2978146

First-level analysis

Failing jobs: WinGet Manifest and Homebrew Cask. Both fail in their post-build artifact-staging step because the expected artifacts/log/Release folder doesn't exist on the agent, which then trips the 1ES non-production-output check. The product build jobs themselves (Windows/linux_/osx_/Publish Assets) only show warnings. Likely category: artifact staging / packaging step not producing the expected log directory on these two manifest jobs.