ROSAENG-1340: Add OSDFM support to rosa-e2e-ocm-fvt ref - #79883
Conversation
Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
|
@dustman9000: This pull request references ROSAENG-1340 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. 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. |
|
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 (2)
WalkthroughThis pull request updates the ROSA OCM FVT test step to add configurable service selection and improve JIRA reporting integration. The step configuration now exports an ChangesOCM FVT Service Parameterization and Reporting
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 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 |
|
[REHEARSALNOTIFIER]
A total of 28 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 periodic-ci-openshift-online-rosa-e2e-main-ocm-fvt-osd-gcp-staging-ocm-fvt-periodic-cs-osd-ccs-gcp-ad-staging-main periodic-ci-openshift-online-rosa-e2e-main-ocm-fvt-rosa-hcp-staging-ocm-fvt-periodic-cs-rosa-hcp-adobe-staging-main periodic-ci-openshift-online-rosa-e2e-main-ocm-fvt-rosa-classic-staging-ocm-fvt-periodic-cs-ocm-resources-staging-main |
|
@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm |
|
/pj-rehearse ack |
|
@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dustman9000, tinaafitz 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 |
088603e
into
openshift:main
) Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
) Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
) Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
) Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
) Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
) Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
) Add OCM_FVT_SERVICE and OCM_FVT_REPORT_JIRA env vars to the shared FVT step registry ref so it can be used for OSDFM tests in addition to CMS tests. - OCM_FVT_SERVICE (default "cms"): ocmtest --service flag - OCM_FVT_REPORT_JIRA (default "true"): controls --reportJiraTicket, ENABLE_JIRA_REPORTING, and jira-cred sourcing Existing CMS tests are unaffected since both default to their current behavior. Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
Summary
Adds
OCM_FVT_SERVICEandOCM_FVT_REPORT_JIRAenv vars to therosa-e2e-ocm-fvtstep registry ref (created in #79840) so it can support OSDFM tests in addition to CMS tests.OCM_FVT_SERVICEcms--serviceflag (cms,osdfm)OCM_FVT_REPORT_JIRAtrue--reportJiraTicketand Jira credential sourcingExisting CMS tests are unaffected since both default to their current behavior.
OSDFM usage example
Jira: https://redhat.atlassian.net/browse/ROSAENG-1340
Test plan
Summary by CodeRabbit
This PR extends the
rosa-e2e-ocm-fvtstep configuration in the OpenShift CI infrastructure to support testing both OCM (Cloud Management) and OSDFM (OSD Fleet Manager) services, previously limited to CMS testing only.Practical Impact:
The changes add two new environment variables to the shared step registry reference:
OCM_FVT_SERVICE: Controls which service the tests run against (cmsorosdfm), defaulting tocmsto maintain backward compatibilityOCM_FVT_REPORT_JIRA: Controls whether Jira ticket reporting is enabled (defaulttrue)Technical Changes:
The implementation refactors the step's shell command script to:
ocmtestcommand arguments based on theOCM_FVT_SERVICEvariableOCM_FVT_REPORT_JIRAAffected Workflows:
Jobs using the shared
rosa-e2e-ocm-fvtstep can now run OSDFM periodic tests by settingOCM_FVT_SERVICE: osdfmandOCM_FVT_REPORT_JIRA: "false", while existing jobs continue to work without modification since the defaults preserve the existing CMS behavior.This change enables broader test coverage for ROSA CI pipelines across multiple service implementations while maintaining the stability of existing test workflows.