ci(agents): bump jira-agent and review-agent CPU/memory requests

[enxebre]

Summary

• Bump CPU requests from 500m to 4 cores and memory from 1Gi to 8Gi for both agent process steps:
  • jira-agent-process (generic jira-agent workflow)
  • hypershift-review-agent-process (HyperShift review agent)

Why

The agent process steps run pre-push hooks that execute make verify + make test -race against 374 Go packages. On 500m (half a CPU core), make test alone takes 30+ minutes and hits the 20-minute Bash tool timeout (exit 143), causing:

1. Push never completes → no remote branch → PR creation fails
2. All work from the solve phase is lost
3. Longer sessions increase the chance of hitting GitHub token expiry
4. Full reruns required, doubling cost

Precedent

The assisted/verify-generated-code step uses cpu: "4" / memory: 3Gi for a similar workload (linters + code generation).

Impact

No change to concurrency — the jira-agent runs once per week processing 1 issue. The review-agent runs on-demand per PR. The Prow cluster autoscales, so this does not reduce capacity for other jobs.

Tracks: CNTRLPLANE-3761

🤖 Generated with Claude Code

Summary by CodeRabbit

• Increased CPU requests from 500m to 4 cores and memory requests from 1Gi to 8Gi for the Jira agent and HyperShift review-agent CI processes.
• Provides sufficient resources for make verify and race-enabled tests across 374 Go packages to finish within the 20-minute hook timeout, without changing concurrency.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 2a5b830f-cdf8-4bf0-af19-9fd4beda0fa7

📥 Commits

Reviewing files that changed from the base of the PR and between 334c674 and bff1368.

📒 Files selected for processing (2)

• ci-operator/step-registry/hypershift/review-agent/process/hypershift-review-agent-process-ref.yaml
• ci-operator/step-registry/jira-agent/process/jira-agent-process-ref.yaml

---

Walkthrough

The HyperShift and Jira agent process definitions now request 4 CPU and 8Gi memory, replacing the previous requests of 500m CPU and 1Gi memory.

Changes

Agent resource updates

Layer / File(s)	Summary
Increase agent resource requests ci-operator/step-registry/hypershift/review-agent/process/hypershift-review-agent-process-ref.yaml, ci-operator/step-registry/jira-agent/process/jira-agent-process-ref.yaml	Both process definitions increase container CPU requests from 500m to 4 and memory requests from 1Gi to 8Gi.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• openshift/release#80927: Introduces the Jira agent generic process step registry at the same reference.

Suggested labels: jira/valid-reference

Suggested reviewers: bryan-cox

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: increasing CPU and memory requests for the Jira and HyperShift review agents.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	Only two step-registry YAML resource requests changed; no Ginkgo test titles were added or modified.
Test Structure And Quality	✅ Passed	PR only changes two step-registry YAML resource requests; no Ginkgo test code or test patterns were modified.
Microshift Test Compatibility	✅ Passed	PR only bumps CPU/memory in two YAML step refs; no new Ginkgo e2e tests or MicroShift-sensitive APIs were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only CI resource YAML changed; no Ginkgo e2e tests were added or modified, so SNO compatibility review is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only CI step resource requests changed; no nodeSelector, affinity, spread, taints, or topology-dependent scheduling logic was introduced.
Ote Binary Stdout Contract	✅ Passed	PR only changes YAML CPU/memory requests in two step-registry refs; no binary/process code or stdout writes are touched.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No Ginkgo/e2e test code changed; the PR only raises CPU/memory requests in two ci-operator YAML refs.
No-Weak-Crypto	✅ Passed	Diff only bumps CPU/memory requests in two YAML refs; no weak crypto, custom crypto, or secret comparisons appear.
Container-Privileges	✅ Passed	The only changed manifests raise resource requests; no privileged, hostPID/Network/IPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings are present.
No-Sensitive-Data-In-Logs	✅ Passed	Only CPU/memory request bumps in two YAML step refs; no logging changes or sensitive data exposure found.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@enxebre: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-hypershift-main-periodic-jira-agent	N/A	periodic	Registry content changed
periodic-ci-openshift-hypershift-main-periodic-review-agent	N/A	periodic	Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[bryan-cox]

/lgtm

[openshift-ci]

@enxebre: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox, enxebre

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/step-registry/hypershift/review-agent/process/OWNERS [bryan-cox,enxebre]
• ci-operator/step-registry/jira-agent/process/OWNERS [bryan-cox,enxebre]

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

[enxebre]

/pj-rehearse ack

[openshift-merge-bot]

@enxebre: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.