Story (Required)

As a QE trying to validate a release, I want to be able to test all the combination matrix, not only the latest GitOps version (1.8.z) into the latest OCP (4.12).

Approach (Required)

We need to implement a system that dynamically generates the information depending on the support matrix (which gitops version needs to be tested in which OCP version) to be retrieved by the CI system, which will gather the IIB information from UMB messages to trigger the proper PipelineRuns that validates the release.

Acceptance Criteria (Mandatory)

• A matrix or table of gitops-operator and ocp version combinations is generated and stored in a relational database to be retrieved later, every time a new IIB is built by CPaaS (UMB triggered).
• An acceptance-tests-release pipeline (within Plumbing Gitops) is launched per each combination of versions.

Done Checklist

• Code is completed, reviewed, documented, and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer-facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met