-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
5
-
False
-
-
False
-
Yes
-
-
-
RHOAM Sprint 53, RHOAM Sprint 54
WHY
As developer I'd like to be confident that each new RHOAM release contains all the required changes and updates to RHOAMs components, in this case, cloud resource operator.
WHAT
After making updates to CRO in: https://issues.redhat.com/browse/MGDAPI-6214 and https://issues.redhat.com/browse/MGDAPI-6233 and <any others?>
HOW
More details on how-to can be found here: https://gitlab.cee.redhat.com/rhcloudservices/integreatly-help/-/blob/master/release/Update_CRO_integreatly-operator.md?ref_type=heads
a) create a PR with updated make file, bundle
b) let the e2e run and pass
c) verify the newly created bundle works with RHOAM
d) merge the CRO PR
e) run the pipeline
Please note, at times, we skip step c) until we have the actual release ready, it simplifies the process but the downside is that it might require re-release if there's something wrong.
TESTS
CRO tests pass
RHOAM and CRO work together with no issues.
DONE
All required PR's for new CRO release are merged
All dependabot PR's for new CRO release are either merged or closed
CRO release works with RHOAM
RHOAM is able to update from previous version of CRO (RHOAM 1.39) to new version of CRO (RHOAM 1.40 - the next RHOAM release) - basically, upgrade scenario of RHOAM works fine.