test-tag-pipeline

Creates manual Konflux PipelineRuns to test tag pipeline changes before merging.

538|560|Updated Jan 18, 2021
One-click install
npx skills add https://github.com/openshift/hypershift --skill test-tag-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-tag-pipeline
Source: https://github.com/openshift/hypershift/tree/main/.claude/skills/test-tag-pipeline
Command: npx skills add https://github.com/openshift/hypershift --skill test-tag-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validating changes to a Konflux tag pipeline normally requires merging a PR and cutting a new tag, which is slow and risky. This Skill lets you test an updated tag pipeline definition against an existing tag's commit before merging, so pipeline fixes can be verified safely.

Core Features & Use Cases

  • Manual PipelineRun Creation: Builds a PipelineRun from a specified branch or fork's pipeline definition targeting an existing tag's commit SHA.
  • Authentication Verification: Checks Konflux login status via oc whoami and provides the login command if needed.
  • Enterprise Contract Validation: After the PipelineRun completes, creates a Snapshot and surfaces the resulting EC PipelineRuns with web UI monitoring URLs.
  • Use Case: A developer fixing the tag pipeline in PR branch build-gomaxprocs-image runs /test-tag-pipeline v0.1.69 build-gomaxprocs-image to confirm the fix rebuilds tag v0.1.69 correctly before merging.

Quick Start

Ask the assistant to test the tag pipeline for tag v0.1.69 using the pipeline definition from your PR branch, then monitor the generated Konflux web UI URL.

Frequently Asked Questions about test-tag-pipeline

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

FAQPage Schema
How do I test a Konflux tag pipeline change before merging?

Run the skill with an existing tag name and optionally the branch containing your updated pipeline, for example /test-tag-pipeline v0.1.69 my-branch. It creates a manual PipelineRun that builds the tag's commit using your updated pipeline definition.

How do I test a pipeline from a forked repository branch?

Pass the branch specification in the format fork:branch-name, such as /test-tag-pipeline v0.1.69 celebdor:OCPBUGS-63194-part2. If no fork is specified, the pipeline is fetched from the openshift repository.

What tools are required to run a manual Konflux PipelineRun?

You need the oc and yq CLI tools installed, and you must be logged into the Konflux instance. If oc whoami fails, log in with oc login --web against the stone-prd-rh01 cluster API endpoint.

How do I trigger Enterprise Contract validation after a PipelineRun?

After the PipelineRun completes successfully, run create-snapshot-from-pipelinerun.sh with the PipelineRun name to create a Snapshot. Then list EC PipelineRuns with oc get pipelinerun filtered by the snapshot label.

Why does the PipelineRun build the old tag commit instead of my branch?

This is intentional: the PipelineRun uses your updated pipeline definition but builds the original tag's commit SHA. This isolates pipeline changes from code changes so you can verify the pipeline fix itself before merging.