What problem does it solve?
Investigating source-build failures in the dotnet/dotnet VMR requires navigating complex CI artifacts, prebuilt package reports, poison leak detection, and multi-repo build ordering, which is difficult without deep knowledge of the source-build pipeline.
Core Features & Use Cases
- Prebuilt Package Analysis: Interpret prebuilt-usage.xml reports to identify which packages lack source-built equivalents and trace them to direct or transitive dependencies.
- Poison and Binary Leak Detection: Diagnose poisoned package leaks and unexpected new binaries flagged by the finish-source-only validation step.
- Stage 2 Build Triage: Investigate failures that occur only in offline stage 2 (bootstrapping) legs that rebuild the product with the source-built SDK.
- Use Case: A CI leg named SB_CentOSStream10_Online_MsftSdk_x64 fails with a prebuilt error. Use this Skill to download the prebuilt-usage.xml from the build artifacts, identify the offending package version, and determine whether it needs an SBRP reference package or a build-order fix.
Quick Start
Investigate why the SB_CentOSStream10_Online_MsftSdk_x64 leg failed in build 20240501.3 and identify the prebuilt packages causing the failure.