skills.rest
eclipse-slm
eclipse-slmOFFICIAL
Explore all skills by this author →
GitHub

get-pr-zuul-results

Fetches Zuul CI build status and log URLs for ansible-collections pull requests.

8|7|Updated Feb 14, 2023
Search Tags:#pull request#troubleshooting#api#build logs#ci status#zuul#ansible-collections
One-click install
npx skills add https://github.com/eclipse-slm/slm --skill get-pr-zuul-results-eclipse-slm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: get-pr-zuul-results
Source: https://github.com/eclipse-slm/slm/tree/main/.agents/skills/get-pr-zuul-results
Command: npx skills add https://github.com/eclipse-slm/slm --skill get-pr-zuul-results-eclipse-slm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Checking Zuul CI results for ansible-collections pull requests requires manually querying the Zuul API, navigating buildsets, and hunting down log URLs for failed jobs. This Skill automates that entire flow and returns a clear summary of build outcomes with direct links to failing job logs. ## Core Features & Use Cases - Buildset Retrieval: Queries the Zuul API for recent buildsets of a PR, showing result, commit, and timing for each. - Failure Analysis: Categorizes builds as SUCCESS, FAILURE, SKIPPED, RETRY, or DEQUEUED and surfaces log and job-output.txt URLs for failed jobs. - Structured Output: Returns failed job names and log links that other workflow skills can consume programmatically. - Use Case: A maintainer asks for the CI status of PR #2974 in ansible-collections/amazon.aws and immediately receives the latest buildset result plus direct links to the failing integration test logs. ## Quick Start Check the Zuul CI status for pull request 2974 and show me the logs of any failed builds.

Frequently Asked Questions about get-pr-zuul-results

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

FAQPage Schema
How do I check Zuul CI status for an ansible-collections pull request?▼

Query the Zuul API buildsets endpoint with the project name and PR number, then fetch the buildset detail by UUID to see individual job results. This Skill automates both calls and summarizes successes, failures, and log URLs.

How to get Zuul build log URLs for a failed job?▼

Each build in a Zuul buildset includes a log_url field when available. The full console output is located at <log_url>/job-output.txt, which this Skill constructs and lists for every failed job.

Can I check Zuul results without knowing the PR number?▼

Yes. If no PR number is provided, the Skill uses the get-pr-number skill to detect the PR from the current git branch, and get-upstream-info to determine the project name, defaulting to ansible-collections/amazon.aws.

What is the difference between Zuul build results FAILURE, SKIPPED, RETRY, and DEQUEUED?▼

FAILURE means the job failed and logs should be examined. SKIPPED means dependencies failed or the job was not applicable. RETRY means the job will rerun automatically. DEQUEUED means the buildset was superseded by a newer commit and can be ignored.

When should I not use this Skill for CI status checks?▼

Do not use it for repositories running GitHub Actions or GitLab CI; use a GitHub Actions results skill instead. It is also not suited for running tests locally, only for querying remote Zuul CI results.

Related Skills

Explore More Software Engineering Skills→
codacy-open-source-projects-scanscodacy-open-source-projects-scans
1

fix-sync

Resolve merge conflicts in ClickHouse sync pull requests using the gh CLI.

Official
Advanced
THRISHAL12345THRISHAL12345

fix-ci-failures

Diagnose failing GitHub Actions checks and isolate CI root causes.

Community
Advanced
zvadaadamzvadaadam
47

greenlight-pr

Automates GitHub PR health by triaging CI failures and bot reviews.

Community
Advanced
apacheapache
79

magpie-flaky-test-triage

Classify GitHub Actions CI jobs as flaky, broken, or clean from run data.

Official
Intermediate