develocity-investigate-test-failures

Generate a structured failure report from Develocity build data.

8|2|Updated Feb 2, 2021

Search Tags:#github-actions #ci #rest-api #test-failures #build-failures #develocity #stacktraces

Ready to run

npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill develocity-investigate-test-failures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: develocity-investigate-test-failures
Source: https://github.com/lhotari/pulsar-contributor-toolbox/tree/main/claude-code/skills/develocity-investigate-test-failures
Command: npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill develocity-investigate-test-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Query the Develocity REST API to identify recent failed builds for a project, extract test and build failures with stack traces, and present a structured failure report. Optionally drill into GitHub Actions artifacts for deeper context.

## Core Features & Use Cases

Query latest failed builds by project, time window, and optional tag filters; extract test and build failures with stack traces.
Inline metadata and links from associated builds to aid triage, including GitHub Actions build URLs and important context.
Drill into GitHub Actions artifacts to retrieve detailed test logs and failure traces for deeper investigation.

### Quick Start Run the develocity-investigate-test-failures tool with your project, days, and optional tag to fetch recent failures and generate a structured report.

Frequently Asked Questions about develocity-investigate-test-failures

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

FAQPage Schema

How do I extract stack traces from recent failed builds using the Develocity REST API?▼

Query the Develocity REST API by project and time window to extract test and build failures with stack traces. Results are scoped by days, max count, and optional tag filters, generating a structured failure report for triage.

Do I need specific environment variables to investigate test failures via the Develocity API?▼

Yes, investigating test failures via the Develocity API requires the DEVELOCITY_SERVER, DEVELOCITY_TOKEN, and DEVELOCITY_PROJECT environment variables to authenticate and fetch data. These must be configured before running the tool.

Can I retrieve detailed test logs from GitHub Actions artifacts when diagnosing CI build failures?▼

Yes, you can optionally drill into GitHub Actions artifacts to retrieve detailed test logs and failure traces for deeper investigation. The tool inlines metadata and links from associated builds including GitHub Actions build URLs.

How do I filter Develocity build failures by specific tags or time windows?▼

Filter Develocity build failures by specifying the days parameter for the time window and adding optional tag filters. You can also limit the maximum number of failed builds returned using the max parameter.

What is the best way to diagnose recent test failures in a CI pipeline using Develocity?▼

The best way to diagnose recent test failures is querying the Develocity REST API to extract failures with stack traces, then drilling into GitHub Actions artifacts for deeper context. This generates a structured failure report with inlined metadata for quick inspection.

Why are my Develocity API queries returning authentication errors when fetching build failures?▼

Develocity API queries return authentication errors when DEVELOCITY_SERVER, DEVELOCITY_TOKEN, or DEVELOCITY_PROJECT environment variables are missing or incorrectly configured. Ensure all three variables are set correctly before fetching data.