microshift-release:automated-testing

Automate MicroShift Phase 2 release testing in Prow CI via draft PRs.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-release-automated-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microshift-release:automated-testing
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-release/skills/automated-testing
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-release-automated-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone process of coordinating MicroShift Phase 2 release testing in Prow CI by guiding you through creating a draft PR, triggering jobs, monitoring results, and publishing artifacts.

Core Features & Use Cases

  • Draft PR orchestration for Phase 2: Creates or reuses a draft PR for the specified MicroShift version and release testing workflow.
  • Prow job lifecycle automation: Triggers applicable CI jobs, verifies completion and scenario outcomes, and validates scenarios against the target version.
  • Artifact retrieval and publication: Downloads job results, uploads them to S3, and closes the PR when cleanup is approved.
  • Use case: For a 4.22.0-rc.1 release candidate, you can run the full workflow to ensure nightly/CI scenarios have passing results, then publish the collected evidence for release readiness.

Quick Start

Run the skill command /microshift-release:automated-testing 4.22.0-rc.1 to execute the full Prow CI release testing workflow for that version.

Frequently Asked Questions about microshift-release:automated-testing

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

FAQPage Schema
How do I automate Microshift Prow CI release testing end-to-end?

Automate Microshift Prow CI release testing by creating or reusing a draft PR, triggering CI jobs, verifying scenario outcomes, and downloading artifacts for upload to S3.

What is the best way to trigger Prow CI jobs for a Microshift release candidate?

Trigger Prow CI jobs for a Microshift release candidate by executing the automated workflow, which initiates applicable CI jobs and continuously verifies completion and scenario outcomes.

Do I need an authenticated gh CLI to run Microshift Phase 2 release testing?

Yes, you need an authenticated gh CLI with openshift/microshift push access, configured aws, and gsutil availability to run Microshift Phase 2 release testing workflows.

How do I upload Microshift release testing artifacts to S3?

Upload Microshift release testing artifacts to S3 by downloading job results from completed Prow CI scenarios and transferring them using the configured aws environment.

Does Microshift release testing automation support version targets older than 4.21?

No, Microshift release testing automation applies exclusively to release testing for version targets 4.21 and newer across all workflow steps.

Can I reuse an existing draft PR for Microshift Prow CI orchestration?

Yes, the Microshift Prow CI orchestration workflow can create a new draft PR or reuse an existing draft PR for the specified release version.