Skip to content

Conversation

@kasturinarra
Copy link

@kasturinarra kasturinarra commented Oct 31, 2025

What this PR does / why we need it:

Add /ci:add-debug-wait command for debugging CI workflows

This command automates creating PRs to add wait steps to OpenShift CI
workflows, enabling QE to debug test failures by pausing execution and
allowing SSH access to the test environment.

Key features:
- Prioritizes job config modifications over workflow modifications
- Uses OCP version to search correct job config files (e.g., release-4.21)
- Adds wait step before last test step (allowing setup steps to complete)
- Auto-commits and auto-pushes changes
- Minimal user prompts (only initial inputs + multi-file selection)
- Clear impact warnings (job config vs workflow scope)

Which issue(s) this PR fixes:

Fixes

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • [ ] Relevant issues have been referenced.
  • This change includes docs.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 31, 2025
@openshift-ci
Copy link

openshift-ci bot commented Oct 31, 2025

Hi @kasturinarra. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kasturinarra kasturinarra force-pushed the raise_pr_debug_cluster branch from 5d11f3a to 6a7b4f7 Compare October 31, 2025 09:32
This command automates creating PRs to add wait steps to OpenShift CI
workflows, enabling QE to debug test failures by pausing execution and
allowing SSH access to the test environment.

Key features:
- Prioritizes job config modifications over workflow modifications
- Uses OCP version to search correct job config files (e.g., release-4.21)
- Adds wait step before last test step (allowing setup steps to complete)
- Auto-commits and auto-pushes changes
- Minimal user prompts (only initial inputs + multi-file selection)
- Clear impact warnings (job config vs workflow scope)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@kasturinarra kasturinarra force-pushed the raise_pr_debug_cluster branch from 6a7b4f7 to 1d6db73 Compare October 31, 2025 09:34
@stbenjam
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 31, 2025
@stbenjam
Copy link
Member

stbenjam commented Nov 3, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 3, 2025
@openshift-ci
Copy link

openshift-ci bot commented Nov 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kasturinarra, stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 3, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 1267a44 into openshift-eng:main Nov 3, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants