ci-analysis

Aggregate CI status for dotnet PRs using Azure DevOps and Helix logs.

18.2k|5.5k|Updated Sep 24, 2019

Search Tags:#logs #ci #azure-devops #pr-analysis #helix #build-failures

Ready to run

npx skills add https://github.com/dotnet/runtime --skill ci-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-analysis
Source: https://github.com/dotnet/runtime/tree/main/.github/skills/ci-analysis
Command: npx skills add https://github.com/dotnet/runtime --skill ci-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyze CI status for dotnet PRs by aggregating Azure DevOps and Helix results to quickly determine PR health and pinpoint failures.

Core Features & Use Cases

Analyze CI build status and test failures across Azure DevOps and Helix for dotnet repositories.
Investigate failing tests, gather logs, and assess whether a PR is ready to merge.
Use with URLs containing dev.azure.com, helix.dot.net, or GitHub PR links to diagnose CI issues.

Quick Start

Run the Get-CIStatus.ps1 script with a PR number or build ID to fetch CI results and logs.

Frequently Asked Questions about ci-analysis

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

FAQPage Schema

How do I analyze Azure DevOps build failures for a dotnet PR?▼

To analyze Azure DevOps build failures, you can run the Get-CIStatus.ps1 script with a PR number or build ID to fetch CI results and pinpoint failing tests for dotnet repositories.

How do I check Helix test logs to see if a PR is ready to merge?▼

You can check Helix test logs by querying the CI status through the analysis script, which aggregates Helix results to assess green or red PR health and gather failure details.

Does this CI analysis work with GitHub PR links or only dev.azure.com URLs?▼

This CI analysis works with GitHub PR links, dev.azure.com URLs, and helix.dot.net links to diagnose build failures, retries, and overall PR health across dotnet repositories.

What is the best way to diagnose failing tests across Azure DevOps and Helix?▼

The best way to diagnose failing tests is to aggregate CI status across Azure DevOps and Helix using the analysis script, which fetches logs and provides recommended actions for failures.

Why do I need access to PR links and Helix logs to analyze CI status?▼

You need access to PR links, builds, and Helix logs because the CI analysis aggregates data from these sources to provide accurate failure details and assess whether the PR is ready to merge.

Can I investigate CI build retries and green or red status for dotnet repositories?▼

Yes, you can investigate CI build retries and green or red status by running the CI status script, which aggregates build data and test failures across Azure DevOps and Helix for dotnet repositories.