OCPBUGS-88732: CCCMO add trigger-only AWS CCM regression presubmit#80829
OCPBUGS-88732: CCCMO add trigger-only AWS CCM regression presubmit#80829RadekManak wants to merge 3 commits into
Conversation
…egression presubmit Add the AWS CCM regression presubmit and keep it trigger-only so it runs only when explicitly requested. Co-authored-by: Cursor <cursoragent@cursor.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: RadekManak The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughA new optional test entry ChangesAWS IPI CCM Regression Test Job
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@RadekManak: This pull request references Jira Issue OCPBUGS-88732, which is valid. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
…esubmit trigger-only Set always_run to false in the source ci-operator config so generated Prow config matches the intended trigger-only behavior. Co-authored-by: Cursor <cursoragent@cursor.com>
…r for metadata Place always_run before as so determinize-ci-operator output matches the source config. Co-authored-by: Cursor <cursoragent@cursor.com>
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse |
|
@RadekManak: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@RadekManak: The following test failed, say
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. |
|
Tests failure is expected. |
|
@RadekManak: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@RadekManak: GitHub didn't allow me to assign the following users: approval, for. Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. DetailsIn response to this:
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. |
Summary
regression-clusterinfra-aws-ipi-ccmpresubmit forcluster-cloud-controller-manager-operatorSummary by CodeRabbit
This PR updates the CI configuration for the
cluster-cloud-controller-manager-operatorrepository to support an AWS-specific CCM regression presubmit that runs on demand.What's changing: A new optional test entry,
regression-clusterinfra-aws-ipi-ccm, is added to thetestslist. It targets AWS IPI using theopenshift-org-awscluster profile and runs theopenshift-e2e-test-clusterinfra-qe-regressionchain via thecucushift-installer-rehearse-aws-ipiworkflow, with CCM-focused selection (E2E_RUN_TAGS=@ccm``,TEST_FILTERS_CLUSTERINFRASTRUCTURE=ccm&&!qe-only, `TEST_SCENARIOS=Cluster_Infrastructure CCM`).Trigger-only behavior: The job is intentionally configured to be trigger-only (not automatically executed on every change) by setting
always_run: falsein the ci-operator source config, matching the existing vSphere regression pattern and avoiding duplicate cross-cloud regression runs. Developers can invoke the AWS regression explicitly when needed via PR comments.