pipelines-health-check

Checks MSBuild CI pipelines, VS insertion PRs, and VMR codeflow PR health.

1.2k|337|Updated Oct 13, 2022
One-click install
npx skills add https://github.com/dotnet/dotnet --skill pipelines-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipelines-health-check
Source: https://github.com/dotnet/dotnet/tree/main/src/msbuild/.github/skills/pipelines-health-check
Command: npx skills add https://github.com/dotnet/dotnet --skill pipelines-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Monitoring MSBuild's CI pipelines, Visual Studio insertion PRs, and VMR codeflow PRs across Azure DevOps and GitHub requires manually checking multiple dashboards and correlating failures with upstream changes, which is slow and error-prone.

Core Features & Use Cases

  • Pipeline Health Overview: Queries the MSBuild and MSBuild-OptProf Azure DevOps pipelines, reports last successful run age, recent run results, and a HEALTHY/FLAKY/UNHEALTHY summary.
  • VS Insertion PR Status: Lists active non-Experimental insertion PRs in the VS repo with check statuses, and flags stale insertions when the last merged PR is too old.
  • VMR Codeflow Monitoring: Finds open codeflow PRs from dotnet/msbuild into dotnet/dotnet, retrieves dotnet-unified-build runs, categorizes failures, and correlates them with the upstream MSBuild PRs that likely caused them.
  • Use Case: Ask for a health check each morning to get status tables for all pipelines and PRs, then have subagents investigate any failing build, categorize root causes (build error, infra, signing), and recommend actions such as retries or reverts.

Quick Start

Ask the assistant to run a health check on the MSBuild pipelines, VS insertion PRs, and VMR codeflow PRs and report any problems.

Frequently Asked Questions about pipelines-health-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Azure DevOps pipeline health from the command line?

Use the az CLI with the azure-devops extension to list recent pipeline runs and query the Build Timeline API for failed tasks. The check-pipeline-health.ps1 script automates this for the MSBuild and MSBuild-OptProf pipelines and outputs JSON.

How do I track VMR codeflow PRs from dotnet/msbuild into dotnet/dotnet?

Search GitHub for open PRs titled "Source code updates from dotnet/msbuild" using the gh CLI, then query the dotnet-unified-build pipeline in dnceng-public for runs on each PR branch. The check-vmr-codeflow.ps1 script does this and correlates failures with upstream PRs.

What prerequisites are needed to run the pipeline health check scripts?

You need the az CLI authenticated with access to the DevDiv organization, the azure-devops extension installed, the gh CLI authenticated for GitHub queries, and PowerShell 5.1 or later. WorkIQ is optional for infrastructure ownership lookups.

Why do VS insertion PR checks show as pending for a long time?

Pending checks are normal for newly created PRs since builds take time to queue and run. If checks remain pending for several hours, it may indicate a stuck pipeline or queue issue worth investigating.

How are VMR build failures categorized and attributed to upstream changes?

Error messages are matched against patterns such as MSB4216 task host errors, CS compilation errors, MSB3073 build command failures, and NuGet or signing issues. Each category is then correlated with upstream MSBuild PRs whose titles match the affected area.