Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
"name": "ci",
"source": "./plugins/ci",
"description": "A plugin to work with OpenShift CI and analyze Prow job results",
"version": "0.0.32"
"version": "0.0.33"
},
{
"name": "teams",
Expand Down
2 changes: 1 addition & 1 deletion docs/data.json
Original file line number Diff line number Diff line change
Expand Up @@ -563,7 +563,7 @@
"name": "Trigger Payload Job"
}
],
"version": "0.0.32"
"version": "0.0.33"
},
{
"commands": [
Expand Down
2 changes: 1 addition & 1 deletion plugins/ci/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "ci",
"description": "Tools for working with OpenShift CI and analyzing Prow job results",
"version": "0.0.32",
"version": "0.0.33",
"author": {
"name": "openshift"
}
Expand Down
4 changes: 3 additions & 1 deletion plugins/ci/skills/analyze-payload/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,9 @@ Wait for all subagents to complete and collect their analysis results. For each

#### 6.1: Correlate Failures with Candidate PRs

For each failed job, cross-reference the failure analysis from the subagent with the candidate PRs from the originating payload. Score each (failed job, candidate PR) pair using the following weighted rubric:
For each failed job, cross-reference the failure analysis from the subagent with the candidate PRs from the originating payload. Additionally, if a subagent traced the root cause to a PR outside the payload (e.g., an `openshift/release` PR that modified a CI step registry script), include that PR as a candidate — it is a regression like any other and should be scored and treated the same way as payload PRs.

Score each (failed job, candidate PR) pair using the following weighted rubric:

Comment thread
stbenjam marked this conversation as resolved.
Resolved
| Signal | Weight | Criteria |
|--------|--------|----------|
Expand Down
1 change: 1 addition & 0 deletions plugins/ci/skills/prow-job-analyze-test-failure/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -336,6 +336,7 @@ The CI system may attach **symptom labels** to job runs — machine-detected pat
- Store artifacts from Prow CI job (json/yaml files) related to the failure under `.work/prow-job-analyze-test-failure/{build_id}/tmp`
- Store logs under `.work/prow-job-analyze-test-failure/{build_id}/logs/`
- Collect evidence from logs and events and other json/yaml files
- **Check for CI step script errors**: If the error is a scripting issue in a CI step (e.g., unbound variable, syntax error, missing command, bad exit code from a shell script) rather than a product bug, check for recent commits to that step's script in the `openshift/release` repository. This is part of evidence gathering — identifying the responsible PR early informs the rest of the analysis. Include the responsible PR in your evidence.

### Step 4.4b: Investigate crash-looping or failing containers

Expand Down