test-tag-pipeline
Skill551 starsChanged 6 months agoApache-2.0View on GitHub
Create a manual PipelineRun to test tag pipeline changes before merging.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api/AGENTS.mdAGENTS.md
- control-plane-operator/AGENTS.mdAGENTS.md
- .cursor/rules/100-go-mistakes.mdcCursor rule
- .cursor/rules/code-formatting.mdcCursor rule
- .cursor/rules/code-review.mdcCursor rule
- .cursor/rules/create-jira-items.mdcCursor rule
- .cursor/rules/debug-aro-hcp-e2e.mdcCursor rule
- .cursor/rules/git-commit-format.mdcCursor rule
- .cursor/rules/restructure-commits.mdcCursor rule
- create-cpo-overrideSkill
- Debug ClusterSkill
- e2e-analyzeSkill
- Effective GoSkill
- feature-developmentSkill
- fix-hypershift-repo-robot-prSkill
- Git Commit FormatSkill
- konflux-buildSkill
- Konflux Archived PipelineRunsSkill
- pr-reportSkill
- restructure-commitsSkill
- triage-leaked-infraSkill
- update-konflux-tasksSkill
- validate-pr-override-imagesSkill
- Git Commit FormatSkill
- restructure-commitsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Create a manual PipelineRun to test tag pipeline changes before merging.
- Very specific: line 13
If no fork specified, defaults to openshift
- Distinctive: line 44
If the authentication check fails, inform the user they need to log in first:
- Distinctive: line 54
After the PipelineRun is created, extract the name from the output and construct the web UI URL:
- Distinctive: line 73
After the Snapshot is created, extract the snapshot name from the output and get the EC PipelineRuns:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create a manual PipelineRun to test tag pipeline changes before merging.
Usage: /test-tag-pipeline <tag-name> [branch-spec]
Arguments:
tag-name(required): The existing tag to rebuild (e.g.,v0.1.69)branch-spec(optional): The branch containing the updated pipeline (defaults tomain)- Format:
[fork:]branch-name - If no fork specified, defaults to
openshift
- Format:
What this does:
- Verifies you are logged into the Konflux instance
- Gets the commit SHA that the tag points to
- Fetches the tag pipeline definition from the specified branch/fork
- Replaces template variables with actual values for the tag
- Creates a manual PipelineRun that uses the updated pipeline to build the tag's commit
- Outputs the PipelineRun name for monitoring
Examples:
# Test main branch pipeline with v0.1.69 tag
/test-tag-pipeline v0.1.69
# Test PR branch pipeline with v0.1.69 tag
/test-tag-pipeline v0.1.69 build-gomaxprocs-image
# Test fork branch pipeline with v0.1.69 tag
/test-tag-pipeline v0.1.69 celebdor:OCPBUGS-63194-part2Implementation:
IMPORTANT: Execute the commands exactly as shown with only the arguments provided by the user. If no branch argument is specified, the template {{args.1:-main}} will correctly default to main. Do NOT substitute the current git branch or any other inferred values.
Step 1: Verify authentication to Konflux
oc whoamiIf the authentication check fails, inform the user they need to log in first:
oc login --web https://api.stone-prd-rh01.pg1f.p1.openshiftapps.com:6443Step 2: Create the PipelineRun
bash hack/tools/scripts/create-manual-tag-pipelinerun.sh {{args.0}} {{args.1:-main}}After the PipelineRun is created, extract the name from the output and construct the web UI URL:
- Base URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com
- Pattern: /ns/crt-redhat-acm-tenant/applications/hypershift-operator/pipelineruns/{pipelinerun-name}
Display the full URL to the user so they can monitor progress in the web UI.
You can also monitor it from the CLI with:
# Watch the PipelineRun status
oc get pipelinerun <name> -wStep 3: After the PipelineRun completes successfully, create a Snapshot to trigger Enterprise Contract validation:
bash hack/tools/scripts/create-snapshot-from-pipelinerun.sh <pipelinerun-name>After the Snapshot is created, extract the snapshot name from the output and get the EC PipelineRuns:
oc get pipelinerun -l appstudio.openshift.io/snapshot=<snapshot-name> -o nameFor each EC PipelineRun, construct and display the web UI URL:
- Base URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com
- Pattern: /ns/crt-redhat-acm-tenant/applications/hypershift-operator/pipelineruns/{ec-pipelinerun-name}
Display the full URLs to the user so they can monitor EC validation in the web UI.
You can also monitor from the CLI with:
# Watch the snapshot status
oc get snapshot <snapshot-name> -w
# Check EC test results
oc get pipelinerun -l appstudio.openshift.io/snapshot=<snapshot-name>Notes:
- This is useful for testing pipeline fixes before merging PRs
- The PipelineRun uses the updated pipeline definition but builds the original tag's commit
- The two-step process allows the PipelineRun to complete (20+ minutes) before creating the Snapshot
- Requires
yqandocCLI tools to be installed - See
hack/tools/scripts/create-manual-tag-pipelinerun.shandhack/tools/scripts/create-snapshot-from-pipelinerun.shfor implementation details
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

