RHDH: route Prow reporter_config to per-release Slack channels#79228
Conversation
Route release branch Prow Slack reporter notifications to dedicated per-release channels (#rhdh-e2e-alerts-1-8, #rhdh-e2e-alerts-1-9) instead of the shared #rhdh-e2e-alerts channel. The main branch continues to use #rhdh-e2e-alerts. This was previously not possible when using the centralized .config.prowgen slack_reporter (see PR openshift#76593). The migration to per-test reporter_config in PR openshift#78976 removed that limitation. Also updates CLAUDE.md new release branch checklist to document the reporter_config channel naming convention. Assisted-by: OpenCode
WalkthroughThis PR updates E2E test job Slack alert channel configurations to use versioned channel names across release branches (1.8 and 1.9), and clarifies the channel setup procedure in documentation. All ChangesVersioned Slack Alert Channels
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 12✅ Passed checks (12 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
zdrapela
changed the title
|
[REHEARSALNOTIFIER]
A total of 60 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse ack |
|
@zdrapela: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-release-1.8.yaml`:
- Line 56: You updated the CI config to set channel: '#rhdh-e2e-alerts-1-8' in
redhat-developer-rhdh-release-1.8.yaml but didn’t regenerate downstream Prow job
artifacts; run the repository make target to regenerate and commit the updated
job configs by running "make update" (or the project’s equivalent), verify the
generated changes include the new reporter channel in the downstream job
manifests, and add those generated files to the same commit so Prow will pick up
the new channel.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: af35df5f-5ec1-4b3b-a407-831cb3c6a79b
⛔ Files ignored due to path filters (2)
ci-operator/jobs/redhat-developer/rhdh/redhat-developer-rhdh-release-1.8-periodics.yamlis excluded by!ci-operator/jobs/**ci-operator/jobs/redhat-developer/rhdh/redhat-developer-rhdh-release-1.9-periodics.yamlis excluded by!ci-operator/jobs/**
📒 Files selected for processing (3)
ci-operator/config/redhat-developer/rhdh/CLAUDE.mdci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-release-1.8.yamlci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-release-1.9.yaml
| presubmit: true | ||
| reporter_config: | ||
| channel: '#rhdh-e2e-alerts' | ||
| channel: '#rhdh-e2e-alerts-1-8' |
There was a problem hiding this comment.
Regenerate Prow job artifacts after CI config edits.
These ci-operator/config changes should be accompanied by regenerated downstream job configs; otherwise the new reporter channels may not be applied by Prow.
As per coding guidelines: After modifying CI configuration files in ci-operator/config/, regenerate downstream artifacts by running make update.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-release-1.8.yaml`
at line 56, You updated the CI config to set channel: '#rhdh-e2e-alerts-1-8' in
redhat-developer-rhdh-release-1.8.yaml but didn’t regenerate downstream Prow job
artifacts; run the repository make target to regenerate and commit the updated
job configs by running "make update" (or the project’s equivalent), verify the
generated changes include the new reporter channel in the downstream job
manifests, and add those generated files to the same commit so Prow will pick up
the new channel.
|
/lgtm |
|
@zdrapela: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: albarbaro, zdrapela The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
try to unstale tide by comment |
|
hey tide |
…hift#79228) Route release branch Prow Slack reporter notifications to dedicated per-release channels (#rhdh-e2e-alerts-1-8, #rhdh-e2e-alerts-1-9) instead of the shared #rhdh-e2e-alerts channel. The main branch continues to use #rhdh-e2e-alerts. This was previously not possible when using the centralized .config.prowgen slack_reporter (see PR openshift#76593). The migration to per-test reporter_config in PR openshift#78976 removed that limitation. Also updates CLAUDE.md new release branch checklist to document the reporter_config channel naming convention. Assisted-by: OpenCode
2 participants
Summary
#rhdh-e2e-alerts-1-8,#rhdh-e2e-alerts-1-9) instead of the shared#rhdh-e2e-alertschannelmainbranch continues to use#rhdh-e2e-alertsCLAUDE.mdnew release branch checklist to document thereporter_configchannel naming conventionContext
The
.config.prowgenfile is deprecated and all functionality has moved to per-testreporter_configfields in ci-operator config YAML. RHDH was already migrated in #78976.Previously, the centralized
.config.prowgenslack_reportercould not route different jobs to different channels (documented in #76593). The per-testreporter_configmodel removes that limitation, allowing each release branch to use its own Slack channel.Jira: https://redhat.atlassian.net/browse/RHIDP-13582