Story (Required)

As a Red Hat engineer trying to release Builds 1.2 I want to ensure all release infrastructure is set up so we can smoothly release Builds 1.2

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

As we are transitioning from CPaaS to Konflux, we need to ensure all release engineering configuration is set up so we can support multiple versions of Builds for OpenShift:

• builds-1.2 - full support
• builds-1.1 - maintenance support
• builds-1.0 - 1 month of maintenance, then EOL

Although the build/test and release pipelines are shifting to Konflux, we still need the CDN and Errata repository to be configured for every version until they can finally be done via Konflux too (not anytime soon). As decided in the Slack Discussion: https://redhat-internal.slack.com/archives/C03CFJBGRTK/p1729176291359209?thread_ts=1729077534.041319&cid=C03CFJBGRTK we will have repo per Y-stream release and same repo will be used for RPM as well as non-RPM releases. As long as CLI is still being released via CPaaS, the repository will need to configured for each release.

Out of scope

<Defines what is not included in this story>

• Enablement of Konflux multi-arch image pipeline
• Quality improvement efforts related to running builds on disconnected clusters.

Open Questions

• Should we build the CLI via Konflux instead of CPaaS? No - we do not have bandwidth to onboard the CLI to Konflux.
• Should we deprecate our "bad" FBC channel names as part of this story? Related story?

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

To kickstart a new release repository, we have to set-up product and release configuration in our midstream in GitLab.

• Copy the previous versions in a new directory and give it the name of the new version. NOTE: this has to be done for all midstream configurations of OpenShift Builds.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

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

• Operator for builds-1.2 able to be released in FBC catalog

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