Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Note: The test-platform-results GCS bucket is publicly accessible - no authentication required.
Quick Start
# Check PR status and get Prow job URLs
gh pr checks <PR_NUMBER>
# Analyze a failed job
/prow-ci <prow-job-url>
# Or ask naturally:"Analyze the lint failure in PR <NUMBER>""Check why the validate job failed""Show me what broke in the coverage job"
Implementation
When invoked, this skill:
Fetches artifacts using fetch_prow_artifacts.py:
Downloads prowjob.json (job metadata)
Downloads (complete build output with all errors)
build-log.txt
Saves to .work/prow-artifacts/<build-id>/
Note: Script is optimized to only download essential files. Optional artifacts (JUnit XML, per-target logs) are skipped as build-log.txt contains all needed information.
Analyzes failures using analyze_failure.py:
Parses build-log.txt for error patterns
Detects common failure patterns (lint, build, timeout, OOM)
# Check latest job status for specific PR
gh pr view PR_NUMBER --json statusCheckRollup --jq '.statusCheckRollup[] | select(.context | contains("prow"))'# Or view all checks for a PR
gh pr checks PR_NUMBER
# Get PR checks
gh pr view PR_NUMBER --json statusCheckRollup
# Find failed jobs
gh pr checks PR_NUMBER | grep -i "fail"# Use this skill to fetch and analyze failures# The script downloads prowjob.json and build-log.txt for analysis
# For unit tests (matches: pull-ci-...-test)
make go-test
# For linting (matches: pull-ci-...-lint)
make go-check
# OR use prek for comprehensive linting
prek run --all-files
# For validation (matches: pull-ci-...-validate)
make validate
# For coverage (matches: pull-ci-...-coverage)
make coverage
# For E2E binary build (matches: pull-ci-...-e2e-binary-build-success)
make e2e-binary-build
# For container builds (Tekton pipelines)
make docker-build
CI/Prow Integration in This Repo
This repo uses both Prow and Tekton for comprehensive CI:
Uses Codecov for coverage reporting (secret: addon-operator-codecov-token)
Skip rules: Changes to .tekton/, GitHub (.github/), .md files, OWNERS, LICENSE don't trigger most jobs
Tekton Pipelines (.tekton/):
Primary build pipeline using Pipelines as Code
Three pipeline types: main, e2e, pko
Builds container images to Quay (addon-operator-tenant)
Pull request images expire after 5 days
Uses boilerplate framework from openshift/boilerplate (docker-build-oci-ta pipeline)
Quick Reference Commands
# Check all PR checks status
gh pr checks <PR_NUMBER>
# View detailed status for a specific PR
gh pr view <PR_NUMBER> --json statusCheckRollup
# Filter only Prow jobs
gh pr checks <PR_NUMBER> | grep "pull-ci-openshift-addon-operator"# Check Tekton pipeline status
gh pr view <PR_NUMBER> --json statusCheckRollup --jq '.statusCheckRollup[] | select(.context | contains("Tekton"))'# Open Prow dashboard in browser (cross-platform)# Copy and paste this URL into your browser:# https://prow.ci.openshift.org/?repo=openshift%2Faddon-operator# Or use platform-specific command:# macOS: open "https://prow.ci.openshift.org/?repo=openshift%2Faddon-operator"# Linux: xdg-open "https://prow.ci.openshift.org/?repo=openshift%2Faddon-operator"# Windows: start "https://prow.ci.openshift.org/?repo=openshift%2Faddon-operator"# View specific PR on Prow (replace <PR_NUMBER>)# https://prow.ci.openshift.org/?repo=openshift%2Faddon-operator&type=presubmit&pull=<PR_NUMBER>
Troubleshooting
Can't find job results?
Check both Prow AND Tekton - this repo uses both systems
# Clone ci-search tool
git clone https://github.com/openshift/ci-search.git
# Use web interface at search.ci.openshift.org (if available)# Search for patterns in build logs across all jobs
