zhongwei/gh-konflux-ci-skills-skills-navigating-github-to-konflux-pipelines
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-30 08:35:21 +08:00
commit 9dbc5f84de
25 changed files with 972 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
tests/results/branch-vs-pr-check-names.1.txt Normal file
View File

@@ -0,0 +1,15 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Good news! The build on the main branch of konflux-ci/yq-container is actually successful. Let me break down the Konflux pipeline checks:
1. "yq-on-push" PipelineRun (Build Check):
- Status: ✅ Succeeded
- PipelineRun URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-push-bfxjq
- Namespace: rhtap-integration-tenant
- Commit SHA: b588d63b2ca3279ba54bd30d5a35fbf882ce3130
2. "yq-container-enterprise-contract" (Integration Test):
- Status: ✅ Succeeded
- PipelineRun URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-container-enterprise-contract-7j4rr
- Note: This check shows 591 successes and 73 warnings, but is still marked as passed
Both Konflux checks on the main branch have passed successfully. There are no failing pipelines to investigate at this time. Would you like me to provide more details about the pipeline runs or explain anything specific about the checks?

20
tests/results/branch-vs-pr-check-names.2.txt Normal file
View File

@@ -0,0 +1,20 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Great news! The checks on the main branch of konflux-ci/yq-container are actually passing. Let me break down the Konflux pipeline results:
1. Konflux On-Push Pipeline:
- Name: `yq-on-push`
- Status: ✅ Succeeded
- PipelineRun: `yq-on-push-bfxjq`
- Namespace: `rhtap-integration-tenant`
- URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-push-bfxjq
2. Enterprise Contract Check:
- Name: `yq-container-enterprise-contract`
- Status: ✅ Succeeded
- PipelineRun: `yq-container-enterprise-contract-7j4rr`
- Namespace: `rhtap-integration-tenant`
- URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-container-enterprise-contract-7j4rr
Note: The enterprise contract check shows 591 successes and 73 warnings, but the overall status is still successful.
There are no failing pipelines on the main branch. Is there a specific issue you're experiencing or would you like me to provide more details about these checks?

21
tests/results/branch-vs-pr-check-names.3.txt Normal file
View File

@@ -0,0 +1,21 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Good news! It appears that the builds are actually successful. There are two Konflux pipelines:
1. **yq-container-enterprise-contract / yq**:
- Status: Completed
- Conclusion: Success
- PipelineRun: [yq-container-enterprise-contract-7j4rr](https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-container-enterprise-contract-7j4rr)
- Note: Has 73 warnings, but overall passed
2. **yq-on-push**:
- Status: Completed
- Conclusion: Success
- PipelineRun: [yq-on-push-bfxjq](https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-push-bfxjq)
- All tasks succeeded
Despite your mention of a failing build, both Konflux pipelines for the main branch show as successful. The second pipeline (yq-on-push) includes multiple checks like security scans, build processes, and other validations, all of which passed.
Would you like me to investigate further? Some potential next steps:
1. Check if you're seeing a specific error not reflected in these pipeline runs
2. Verify the exact commit SHA you're concerned about
3. Look into the warnings in the enterprise-contract pipeline

11
tests/results/extract-build-pipelinerun-url.1.txt Normal file
View File

@@ -0,0 +1,11 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I've retrieved the PipelineRun URL for you. Here are the details:
PipelineRun URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8
Parsed components:
- Cluster: konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com
- Namespace: rhtap-integration-tenant
- PipelineRun Name: yq-on-pull-request-69sq8
Note: The check actually shows as "pass" in the PR checks, so it seems the build was successful. Would you like me to help you investigate any specific aspect of this PipelineRun?

14
tests/results/extract-build-pipelinerun-url.2.txt Normal file
View File

@@ -0,0 +1,14 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I apologize for the confusion. The checks are actually showing as "SUCCESS" for this PR. Could you clarify:
1. Are you certain the 'yq-on-pull-request' check failed?
2. Do you want me to retrieve the PipelineRun URL anyway?
If the check did fail, the PipelineRun URL would be:
`https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8`
Parsed details:
- Cluster: konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com
- Namespace: rhtap-integration-tenant
- PipelineRun: yq-on-pull-request-69sq8
Could you provide more context about the failed check you're seeing?

14
tests/results/extract-build-pipelinerun-url.3.txt Normal file
View File

@@ -0,0 +1,14 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I see the PipelineRun URL directly in the check details. Let me extract it for you:
The PipelineRun URL is:
`https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8`
Breaking down the URL:
- Cluster: konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com
- Namespace: rhtap-integration-tenant
- PipelineRun Name: yq-on-pull-request-69sq8
Note: The check actually shows as "pass", not "fail" as you mentioned. This could mean the check has been fixed since you last checked, or there might be a misunderstanding about the check status.
Would you like me to help you investigate further or provide more details about this PipelineRun?

8
tests/results/extract-integration-test-pipelinerun-url.1.txt Normal file
View File

@@ -0,0 +1,8 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Let me parse the URL details for you:
- **Cluster**: konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com
- **Namespace**: rhtap-integration-tenant
- **PipelineRun Name**: functional-test-78db6
You can use these details to further investigate the failed functional test. Would you like me to help you debug the PipelineRun using kubectl?

10
tests/results/extract-integration-test-pipelinerun-url.2.txt Normal file
View File

@@ -0,0 +1,10 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
To debug this further, you'll want to use the kubectl command to describe the PipelineRun in the rhtap-integration-tenant namespace. The full command would be:
```bash
kubectl describe pipelinerun functional-test-78db6 -n rhtap-integration-tenant
```
This will give you detailed information about why the functional test failed, including any error messages, task statuses, and potential reasons for the failure.
Would you like me to help you investigate the specific failure details of this PipelineRun?

10
tests/results/extract-integration-test-pipelinerun-url.3.txt Normal file
View File

@@ -0,0 +1,10 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Let me parse the PipelineRun URL details:
- **Cluster**: konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com
- **Namespace**: rhtap-integration-tenant
- **PipelineRun Name**: functional-test-78db6
To debug this further, you can use kubectl to inspect the PipelineRun in the specified cluster and namespace. The next step would be to use the debugging-pipeline-failures skill to get more details about why the functional test failed.
Would you like me to help you investigate the specific failure reasons for this PipelineRun?

32
tests/results/parse-pipelinerun-url-components.1.txt Normal file
View File

@@ -0,0 +1,32 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I'll help you extract the information from the Konflux URL. I'll use the navigating-github-to-konflux-pipelines skill to assist with this.
<invoke name="Skill">
<parameter name="skill">navigating-github-to-konflux-pipelines</parameter>
</invoke>
Let me break down the URL for you:
- Cluster: `stone-prd-rh01.pg1f.p1.openshiftapps.com`
- Namespace: `rhtap-integration-tenant`
- PipelineRun name: `yq-on-pull-request-69sq8`
You can use these values in kubectl commands like this:
```bash
kubectl get pipelinerun yq-on-pull-request-69sq8 -n rhtap-integration-tenant -c stone-prd-rh01.pg1f.p1.openshiftapps.com
```
To make this easier, you can set these as environment variables:
```bash
export CLUSTER=stone-prd-rh01.pg1f.p1.openshiftapps.com
export NAMESPACE=rhtap-integration-tenant
export PIPELINERUN=yq-on-pull-request-69sq8
```
Then use them in commands like:
```bash
kubectl get pipelinerun $PIPELINERUN -n $NAMESPACE -c $CLUSTER
```
Is there a specific kubectl command you'd like to run with these details?

26
tests/results/parse-pipelinerun-url-components.2.txt Normal file
View File

@@ -0,0 +1,26 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Great! For your Konflux URL `https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8`, I'll extract the details for you using the parsing method described in the skill documentation:
```bash
url="https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8"
cluster=$(echo "$url" | sed 's|https://\([^/]*\).*|\1|')
namespace=$(echo "$url" | sed 's|.*/ns/\([^/]*\).*|\1|')
pipelinerun=$(echo "$url" | sed 's|.*/pipelinerun/\([^/?]*\).*|\1|')
echo "Cluster: $cluster"
echo "Namespace: $namespace"
echo "PipelineRun: $pipelinerun"
```
These values are:
- Cluster: `konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com`
- Namespace: `rhtap-integration-tenant`
- PipelineRun: `yq-on-pull-request-69sq8`
You can now use these with kubectl commands, for example:
```bash
kubectl get pipelinerun yq-on-pull-request-69sq8 -n rhtap-integration-tenant
```
Would you like me to help you investigate this PipelineRun further?

25
tests/results/parse-pipelinerun-url-components.3.txt Normal file
View File

@@ -0,0 +1,25 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I'll help you extract the cluster, namespace, and PipelineRun name from the Konflux URL you provided.
From the URL: `https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8`
I'll parse it using the script's recommended method:
```bash
url="https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8"
cluster=$(echo "$url" | sed 's|https://\([^/]*\).*|\1|')
namespace=$(echo "$url" | sed 's|.*/ns/\([^/]*\).*|\1|')
pipelinerun=$(echo "$url" | sed 's|.*/pipelinerun/\([^/?]*\).*|\1|')
```
Here's the breakdown:
- **Cluster**: `konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com`
- **Namespace**: `rhtap-integration-tenant`
- **PipelineRun**: `yq-on-pull-request-69sq8`
You can now use these values in kubectl commands like:
```bash
kubectl get pipelinerun yq-on-pull-request-69sq8 -n rhtap-integration-tenant
```
Would you like me to help you debug this PipelineRun or do you need anything else?

12
tests/results/pr-failing-checks-llm-compressor.1.txt Normal file
View File

@@ -0,0 +1,12 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I apologize for the confusion. Let me summarize what I've found:
1. The Konflux pipeline `llm-compressor-on-pull` is failing for PR #12
2. The PipelineRun URL is: https://konflux-ui.apps.kflux-prd-rh03.nnv1.p1.openshiftapps.com/ns/konflux-ai-sig-tenant/pipelinerun/llm-compressor-on-pull-9z9gf
To help you debug, I recommend:
1. Visit the PipelineRun URL to see detailed failure logs
2. Check the specific stage or task that caused the pipeline to fail
3. Review the error messages in the pipeline details
Would you like me to help you investigate the specific failure reason by guiding you through the PipelineRun details?

14
tests/results/pr-failing-checks-llm-compressor.2.txt Normal file
View File

@@ -0,0 +1,14 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I apologize for the confusion. Let me summarize what I've found:
The Konflux pipeline for PR #12 in ralphbean/llm-compressor-hermetic-demo is failing. Specifically:
- Pipeline Name: llm-compressor-on-pull
- Status: Fail
- PipelineRun URL: https://konflux-ui.apps.kflux-prd-rh03.nnv1.p1.openshiftapps.com/ns/konflux-ai-sig-tenant/pipelinerun/llm-compressor-on-pull-9z9gf
To investigate further, I recommend:
1. Check the PipelineRun URL to see detailed logs of the failing pipeline
2. Review the specific test or build step that caused the failure
3. Look at the error messages in the PipelineRun details
Would you like me to help you dig deeper into the specific failure reasons?

13
tests/results/pr-failing-checks-llm-compressor.3.txt Normal file
View File

@@ -0,0 +1,13 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
I've found the failing Konflux pipeline for your PR. Here are the key details:
1. Check Name: "Konflux kflux-prd-rh03 / llm-compressor-on-pull"
2. Conclusion: FAILURE
3. PipelineRun URL: https://konflux-ui.apps.kflux-prd-rh03.nnv1.p1.openshiftapps.com/ns/konflux-ai-sig-tenant/pipelinerun/llm-compressor-on-pull-9z9gf
Parsing the PipelineRun URL:
- Cluster: konflux-ui.apps.kflux-prd-rh03.nnv1.p1.openshiftapps.com
- Namespace: konflux-ai-sig-tenant
- PipelineRun Name: llm-compressor-on-pull-9z9gf
The build check for your PR has failed. To investigate further, I recommend using the debugging-pipeline-failures skill to get more details about why the pipeline failed. Would you like me to help you dig deeper into the specific failure reasons?

17
tests/results/pr-filter-non-konflux-checks.1.txt Normal file
View File

@@ -0,0 +1,17 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Here are the details of the two failing Konflux checks:
1. Enterprise Contract Check:
- PipelineRun: oras-container-enterprise-contract-9lkhf
- Status: FAILURE
- Details: 327 successes, 30 warnings, 6 failures
- Logs: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/oras-container-enterprise-contract-9lkhf/logs/verify
2. Functional Test:
- PipelineRun: functional-test-78db6
- Status: FAILURE
- Logs: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/functional-test-78db6/logs/functional
I recommend investigating these two PipelineRuns to understand why the checks are failing. The Enterprise Contract check seems to have some specific failures (6 out of 357 checks), while the Functional Test has a general failure.
Would you like me to help you dig deeper into the reasons for these check failures?

24
tests/results/pr-filter-non-konflux-checks.2.txt Normal file
View File

@@ -0,0 +1,24 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
Based on the investigation, there are two Konflux checks that failed for PR #249:
1. **Red Hat Konflux / functional-test / oras-container**
- PipelineRun URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/functional-test-78db6
- Status: Failed
- Details: The functional test task failed without specific error details
2. **Red Hat Konflux / oras-container-enterprise-contract / oras-container**
- PipelineRun URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/oras-container-enterprise-contract-9lkhf
- Status: Failed
- Details: The verify task failed with:
- 327 successes
- 30 warnings
- 6 failures
In contrast, the build check **Red Hat Konflux / oras-container-on-pull-request** passed successfully.
To investigate further, you would need to:
1. Check the detailed logs for the functional test PipelineRun
2. Investigate the 6 failures in the enterprise contract verification
3. Review the warnings and specific failure details in the PipelineRun URLs provided
Would you like me to help you dig deeper into these specific failures?

16
tests/results/pr-filter-non-konflux-checks.3.txt Normal file
View File

@@ -0,0 +1,16 @@
# skill_digest: f15347d6f22704568ffc3656768cb503c13f92a22a775a59d9b0fda007964bfb
To summarize the Konflux checks for PR #249 in konflux-ci/oras-container:
Failing Checks:
1. Functional Test: "Red Hat Konflux / functional-test / oras-container"
2. Enterprise Contract: "Red Hat Konflux / oras-container-enterprise-contract / oras-container"
Passing Check:
- Build Pipeline: "Red Hat Konflux / oras-container-on-pull-request"
The PipelineRun URL for the build check is:
`https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/oras-container-on-pull-request-l2nxk`
You should investigate the failures in the functional test and enterprise contract checks. These typically indicate issues with the code's functionality or compliance with enterprise contracts.
Would you like me to help you dig deeper into these specific failing checks?

93
tests/scenarios.yaml Normal file
View File

@@ -0,0 +1,93 @@
# Test scenarios for navigating-github-to-konflux-pipelines skill
# This file defines all test cases for validating the skill's behavior
skill_name: navigating-github-to-konflux-pipelines
description: Tests for GitHub check navigation and PipelineRun URL extraction
# Paths to copy from real HOME to test environment HOME
# This skill needs GitHub CLI authentication to run gh commands
copy_to_home:
- .config/gh
# Test scenarios following TDD methodology (RED-GREEN-REFACTOR)
test_scenarios:
- name: pr-failing-checks-llm-compressor
description: Test finding Konflux checks from a real PR in llm-compressor-hermetic-demo
prompt: "I'm working on PR #12 in ralphbean/llm-compressor-hermetic-demo and the checks are failing. Can you help me find which Konflux pipeline is failing?"
model: haiku
samples: 3
expected:
contains_keywords:
- pipeline
does_not_contain:
- cannot help
baseline_failure: "Agent doesn't know how to query GitHub checks or filter for Konflux"
- name: pr-filter-non-konflux-checks
description: Test filtering out non-Konflux checks (Prow, SonarCloud, etc)
prompt: "PR #249 in konflux-ci/oras-container has several failing checks. Which ones are Konflux checks I should investigate?"
model: haiku
samples: 3
expected:
contains_keywords:
- Konflux
- checks
does_not_contain:
- ci/prow
- SonarCloud
- tide
- dco
baseline_failure: "Agent includes non-Konflux checks or doesn't know how to filter"
- name: extract-build-pipelinerun-url
description: Test extracting PipelineRun URL from build check
prompt: "The build check 'yq-on-pull-request' failed on PR #206 in konflux-ci/yq-container. Can you get me the PipelineRun URL?"
model: haiku
samples: 3
expected:
contains_keywords:
- konflux-ui.apps
- "https://"
does_not_contain: []
baseline_failure: "Agent doesn't know build checks have direct URLs in details_url"
- name: extract-integration-test-pipelinerun-url
description: Test extracting PipelineRun URL from integration test check
prompt: "The 'functional-test' integration test failed on PR #249 in konflux-ci/oras-container. How do I get the PipelineRun details?"
model: haiku
samples: 3
expected:
contains_keywords:
- pipelinerun
- namespace
does_not_contain:
- gh api
baseline_failure: "Agent doesn't know to extract URL from check output.text"
- name: parse-pipelinerun-url-components
description: Test parsing cluster, namespace, and PipelineRun name from URL
prompt: "I have this Konflux URL: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/rhtap-integration-tenant/pipelinerun/yq-on-pull-request-69sq8 - how do I extract the cluster, namespace, and PipelineRun name for kubectl commands?"
model: haiku
samples: 3
expected:
contains_keywords:
- namespace
- rhtap-integration-tenant
- yq-on-pull-request-69sq8
does_not_contain: []
baseline_failure: "Agent doesn't know how to parse URL components"
- name: branch-vs-pr-check-names
description: Test understanding -on-push vs -on-pull-request naming
# The build is actually successful!
prompt: "The build is failing on the main branch of konflux-ci/yq-container. How do I find the failing Konflux pipeline?"
model: haiku
samples: 3
expected:
contains_keywords:
- "https://konflux-ui.app"
- actually
does_not_contain:
- on-pull-request
- gh api
baseline_failure: "Agent looks for -on-pull-request instead of -on-push for branch builds"