ci-pipeline-monitor

Monitors Azure DevOps CI test pipelines and triages failures against GitHub issues.

18.2k|5.6k|Updated Sep 24, 2019
One-click install
npx skills add https://github.com/dotnet/runtime --skill ci-pipeline-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-pipeline-monitor
Source: https://github.com/dotnet/runtime/tree/main/.github/skills/ci-pipeline-monitor
Command: npx skills add https://github.com/dotnet/runtime --skill ci-pipeline-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Tracking test failures across dozens of .NET runtime CI pipelines on Azure DevOps is manual and error-prone. This Skill automates fetching build results, extracting every failed test via the AzDO Test Results API, downloading Helix console logs, and correlating failures with existing GitHub issues.

Core Features & Use Cases

  • Automated failure extraction: Fetches latest builds from 20+ pipelines, extracts every failed test method, and downloads full Helix console logs into a local SQLite database.
  • Agent-driven triage: Classifies failures by exit code and error message, groups them by root cause, and searches dotnet/runtime GitHub issues for matches.
  • Report generation and bisection: Produces a formatted weekly test report with action items and can bisect regressions to identify the commit or PR that introduced a failure.
  • Use Case: Ask the agent to check the CI test pipelines; it runs the full pipeline end-to-end and outputs a report listing each failure group, its matching GitHub issue, and new failures needing issues filed.

Quick Start

Ask the agent to check the CI test pipelines and generate the weekly CI test report.

Frequently Asked Questions about ci-pipeline-monitor

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

FAQPage Schema
How do I monitor Azure DevOps CI pipeline test failures automatically?

Run the skill from the dotnet/runtime repo root in Copilot CLI. It fetches the latest build per pipeline via the AzDO Builds API, extracts failed tests via the Test Results API, downloads Helix console logs, and generates a triage report.

How do I extract failed test results from Azure DevOps builds?

The extract_failed_tests.py script queries the AzDO Test Results API for each failing build and inserts one row per failed test method into a SQLite database. It requires an ADO_TOKEN bearer token obtained via az account get-access-token.

Does the AzDO Test Results API require authentication on dnceng-public?

Yes, the Test Results API returns a 203 sign-in page without a bearer token even on the public dnceng org. The Builds API and Helix API are public and require no authentication.

Why does the Build Timeline API miss individual test failures?

The Timeline API reports at work-item level only and silently misses individual test failures within a Helix work item. The skill bans it and always uses the AzDO Test Results API for complete failure extraction.

Can the skill file or match GitHub issues for CI failures?

Yes, during triage the agent searches dotnet/runtime issues via GitHub MCP tools, matches failures to existing issues, and flags unmatched failures as NEW with a pre-formatted issue body in the report.