rc-test

Launches and monitors Prow CI jobs for OpenShift edge topology release candidate testing, generating Jira-ready reports of failures.

7|15|Updated Jan 23, 2026

Search Tags:#automation #continuous integration #failure triage #prow ci #release candidate testing #edge topologies #jira reporting

Ready to run

npx skills add https://github.com/openshift-eng/edge-tooling --skill rc-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rc-test
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/edge-ocp-rc/skills/rc-test
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill rc-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It removes the manual overhead of launching, monitoring, and interpreting release candidate CI results for OpenShift edge topologies, so failures can be investigated and reported quickly.

Core Features & Use Cases

Launch and monitor RC job suites: Start Prow CI jobs for TNF, TNA, or SNO, then watch progress and summarize outcomes.
Investigate failures with classification: Convert failed job signals into categorized findings and correlate patterns across topologies.
Generate Jira-ready reporting: Produce markdown suitable for posting back to the appropriate Jira ticket.

Quick Start

Ask rc-test to launch and monitor TNF release candidate jobs for rc.0, then generate a Jira-ready report of any failures.

Frequently Asked Questions about rc-test

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

FAQPage Schema

How do I automate Prow CI job launches for OpenShift edge release candidate testing?▼

You can automate OpenShift edge release candidate testing by using this Skill to launch and monitor Prow CI jobs for TNF, TNA, and SNO topologies. It handles job initiation, status monitoring, and summarizes outcomes.

How do I triage Prow CI failures across OpenShift edge topologies like TNF and SNO?▼

To triage Prow CI failures, this Skill investigates failed job signals and converts them into categorized findings. It correlates failure patterns across TNF, TNA, and SNO topologies to help you identify root causes.

Can I generate Jira-ready reports directly from OpenShift release candidate CI results?▼

Yes, you can generate Jira-ready reports from your release candidate results. This Skill produces markdown summaries of failed jobs suitable for posting back to Jira tickets using the MCP Jira tool.

Do I need Jira comment permissions to run release candidate triage and reporting?▼

You need Jira comment permissions through the MCP Jira tool to use the reporting action. This allows the Skill to post the generated markdown failure summaries directly to the appropriate Jira tickets.

What actions are available for managing OpenShift release candidate validation cycles?▼

Available actions for OpenShift release candidate validation include list, refresh, launch, status, report, and investigate. You select these actions along with topology and version parameters to manage the full cycle.

When should I relaunch failed Prow CI jobs during edge topology release validation?▼

You should relaunch failed Prow CI jobs during edge topology release validation when the investigate action reveals transient or infrastructure-related failures. This Skill supports optional relaunching of failed jobs after initial failure analysis.