Story (Required)

As a release engineer doing 1.15.0 release, I want to remove the build configurations in CPaaS that are no longer maintained, so that only the required resources are utilized.

Background (Required)

When 1.15.0, releases, 1.12.0 goes out of maintenance automatically. The CPaaS build configurations should be updated to remove these branch builds from Jenkins.

Out of scope

N/A

Approach (Required)

• Fork and Clone the repo https://gitlab.cee.redhat.com/cpaas-products/product-configs/-/blob/main/openshift-gitops/openshift-gitops.yml?ref_type=heads#L21
• add gitops-1.11-rhel-8 and gitops-1.12-rhel-8 to the excluded_branches field.
• Submit a merge request (MR) and after sucessful test run the MR would be merged automatically.
• Check the jenkins web console hosted by CPaaS and see that the build configurations for older versions are gone.
  https://jenkins-cpaas-openshift-gitops.apps.cpaas-poc.r6c9.p1.openshiftapps.com/

Dependencies

Release for 1.15.0 is complete and the errata is in SHIPPED_LIVE state.

Acceptance Criteria (Mandatory)

Build configurations for 1.11.0 are not seen in the CPaaS Jenkins Web console.
https://jenkins-cpaas-openshift-gitops.apps.cpaas-poc.r6c9.p1.openshiftapps.com/

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

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