skills.rest
DataDog
DataDogOFFICIAL
Explore all skills by this author →
Website𝕏@datadoghqGitHub

analyze-azdo-build

Analyze Azure DevOps CI build failures and categorize issues by pull request or build ID.

570|166|Updated Aug 30, 2017
Search Tags:#debugging#troubleshooting#dotnet#build failures#azure devops#ci
One-click install
npx skills add https://github.com/DataDog/dd-trace-dotnet --skill analyze-azdo-build
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-azdo-build
Source: https://github.com/DataDog/dd-trace-dotnet/tree/main/.claude/skills/analyze-azdo-build
Command: npx skills add https://github.com/DataDog/dd-trace-dotnet --skill analyze-azdo-build

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers quickly understand and resolve failures in Azure DevOps CI builds for the dd-trace-dotnet repository, reducing debugging time and improving pipeline stability.

Core Features & Use Cases

  • Automated Analysis: Identifies the root cause of build failures, categorizing them into infrastructure, flaky, or real issues.
  • Actionable Recommendations: Provides specific steps to fix the problem, including retrying stages, updating snapshots, or investigating code.
  • Use Case: When a pull request fails its CI checks, use this Skill with the PR number to get an immediate breakdown of the failures and suggested next steps.

Quick Start

Use the analyze-azdo-build skill to analyze the failures for pull request 7806.

Frequently Asked Questions about analyze-azdo-build

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

FAQPage Schema
How do I debug Azure DevOps CI build failures for a dotnet repository?▼

To debug Azure DevOps CI build failures, you can analyze pull request numbers or build IDs to categorize issues as infrastructure, flaky, or real, and receive actionable recommendations to resolve them.

What causes flaky build failures in Azure DevOps CI pipelines?▼

Flaky build failures in Azure DevOps CI are identified by analyzing deep pipeline logs, distinguishing transient infrastructure issues from real code defects to recommend appropriate retry or investigation steps.

Do I need PowerShell and Azure CLI to troubleshoot Azure DevOps build failures?▼

Yes, troubleshooting Azure DevOps build failures requires PowerShell 7+, GitHub CLI, and Azure CLI with the azure-devops extension to inspect logs and automate retries of failed stages.

Can I automatically retry failed Azure DevOps CI stages?▼

Yes, you can automatically retry failed Azure DevOps CI stages by analyzing the build ID, which inspects failure logs and executes targeted retries for stages categorized as flaky or infrastructure issues.

What is the best way to analyze pull request CI failures in Azure DevOps?▼

The best way to analyze pull request CI failures in Azure DevOps is using automated log inspection to identify root causes and provide specific steps like updating snapshots or investigating code changes.

Related Skills

Explore More Software Engineering Skills→
ajilantonyajilantony

azure-devops-cli

Manage Azure DevOps resources through the Azure CLI extension.

Community
Advanced
sergeyitalysergeyitaly
1

github-actions-ci

Debug GitHub Actions pipeline failures and reproduce CI jobs locally with act.

Community
Intermediate
RedtropigRedtropig
14

self-correction-loop

Automate evidence-first correction loops after lint, test, or build failures.

Community
Advanced
lewinglewing
4

ci-analysis

Analyze Azure DevOps and Helix CI failures for dotnet repository PRs.

Community
Advanced