feat: register CAPA e2e full lifecycle job in ci-status-jobs

[andclt]

Description

Register the new weekly CAPA e2e full lifecycle periodic job in ci-status-jobs.yaml so it appears in the Slack CI summary and rosa-eng-dashboard alongside the existing smoke job.

Depends on: openshift/release#82914 (adds the periodic job to the release repo)

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• CI/CD or tooling change

Testing

• Manual verification completed

The prow filter already uses a wildcard (*rosa-e2e-main_capa-e2e*) that matches the new job name. This change only adds the job entry for dashboard tracking.

Checklist

• My code follows the project's coding conventions
• I have updated documentation as needed
• I have added tests that prove my fix/feature works
• All new and existing tests pass

Summary by CodeRabbit

• New Features
  • Added the CAPA E2E Full Lifecycle job to the staging end-to-end test suite.
  • Enabled tracking of the job’s CI status in the staging category.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: andclt
Once this PR has been reviewed and has the lgtm label, please assign dustman9000 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift-online/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a2ee26b0-461a-4f1c-996d-7a8d4df7608c

📥 Commits

Reviewing files that changed from the base of the PR and between dd0adc5 and 8cbba83.

📒 Files selected for processing (1)

• configs/ci-status-jobs.yaml

---

Walkthrough

The CI status configuration adds the CAPA E2E Full Lifecycle job to the capa-e2e-stg category and maps it to its corresponding Prow job identifier.

Changes

CAPA E2E CI status tracking

Layer / File(s)	Summary
Configure CAPA lifecycle job configs/ci-status-jobs.yaml	The capa-e2e-stg category now tracks the CAPA E2E Full Lifecycle Prow job.

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

Possibly related PRs

• openshift-online/rosa-e2e#82: Adds the staging CI job category used by this configuration.
• openshift-online/rosa-e2e#162: Updates the same capa-e2e-stg CI status category.
• openshift-online/rosa-e2e#165: Adds another CAPA E2E job to the same staging category.

Suggested labels: lgtm, approved

Suggested reviewers: bmeng, dustman9000, tiwillia

🚥 Pre-merge checks | ✅ 11

✅ Passed checks (11 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: registering the CAPA E2E full lifecycle job in ci-status-jobs.
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.
No-Weak-Crypto	✅ Passed	The only PR changes add a CAPA job name and Prow job identifier in YAML; no weak crypto, custom crypto, or secret comparison code is introduced.
Container-Privileges	✅ Passed	The commit adds only a job name and prow_job string in configs/ci-status-jobs.yaml; it adds no container or Kubernetes privilege settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR adds only a display name and public Prow job identifier; the diff contains no password, token, API key, PII, session ID, or customer data.
No-Hardcoded-Secrets	✅ Passed	The two added YAML values are a job display name and a Prow job identifier; scans found no secret-like assignments, credential URLs, private keys, or base64 strings.
No-Injection-Vectors	✅ Passed	The PR only modifies configs/ci-status-jobs.yaml, a static YAML configuration file. The two added lines define static job metadata without any injection vectors: no SQL concatenation, shell=True, e...
Ai-Attribution	✅ Passed	No AI tool usage mentioned in PR or commits. The contributor authored the PR with manual verification only. Attribution check not applicable when AI use is not claimed.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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