fetch-payloads

Fetch Payloads

This skill fetches recent release payloads from the OpenShift release controller, showing their tag name, acceptance phase, timestamp, blocking job results, and a link to the release details page.

When to Use This Skill

Use this skill when you need to:

• Find the latest accepted (or rejected) nightly or CI payloads for a given OCP version
• Check the current state of release payloads for any architecture
• See which blocking jobs failed for rejected payloads
• Get a link to the release controller page for a specific payload

Implementation Steps

Step 1: Determine defaults

If the user did not specify an architecture or stream, default to amd64 and nightly. If no version is specified, the script automatically fetches the latest from the Sippy API.

Step 2: Fetch payloads

FETCH_PAYLOADS="${CLAUDE_PLUGIN_ROOT}/skills/fetch-payloads/fetch_payloads.py"
if [ ! -f "$FETCH_PAYLOADS" ]; then
  FETCH_PAYLOADS=$(find ~/.claude/plugins -type f -path "*/ci/skills/fetch-payloads/fetch_payloads.py" 2>/dev/null | sort | head -1)
fi
if [ -z "$FETCH_PAYLOADS" ] || [ ! -f "$FETCH_PAYLOADS" ]; then echo "ERROR: fetch_payloads.py not found" >&2; exit 2; fi
python3 "$FETCH_PAYLOADS" [architecture] [version] [stream]

Examples:

# Latest amd64 nightly payloads (all defaults, last 5)
python3 "$FETCH_PAYLOADS"

# arm64 4.18 nightly
python3 "$FETCH_PAYLOADS" arm64 4.18 nightly

# Only accepted payloads
python3 "$FETCH_PAYLOADS" amd64 4.18 nightly --phase Accepted

# Show more results
python3 "$FETCH_PAYLOADS" amd64 4.18 nightly --limit 20

Step 3: Present results

The script outputs one block per payload to stdout with job details. Present to the user as-is or summarize.

Output Format

The script outputs a JSON object to stdout:

{
  "hours_since_last_accepted": 23.5,
  "last_accepted_tag": "4.22.0-0.nightly-2026-02-24-030944",
  "payloads": [ ... ]
}

• hours_since_last_accepted: Hours since the most recent Accepted payload in the stream (from the full unfiltered history), or null if none found.
• last_accepted_tag: Tag name of the most recent Accepted payload, or null if none found.
• payloads: Array of payload objects, each containing tag, phase, release controller URL, and job results (blocking and async jobs with Prow URLs and retry details).