Story (Required)

As a cluster admin trying to install OpenShift Builds I want the operator to deploy productized versions of Shipwright

<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>

In BUILD-719, we are bootstrapping a "dummy" operator that doesn't deploy any operand. In order to release a product, we need the operands to be built in a productized build system.

Out of scope

<Defines what is not included in this story>

• Re-productize the CSI driver images - see SRCD-5
• Deploy shared resources via the OpenShift Builds operator - see SRCD-29
• Deploy productized images - see BUILD-720
• Run upstream shipwright-io/build tests as part of integration test suite.

Approach (Required)

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

• Fork shipwright-io/build into our Red Hat owned GitHub organization (redhat-openshift-builds). Fork name should be shipwright-io-build).
• Create a branch for the next release in our fork, with a naming scheme independent of Shipwright's release branching (ex: builds-1.1).
• Onboard the images for this repo as a components in Konflux. shipwright-io/build produces multiple container images.

Dependencies

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

• BUILD-719 - bootstrap GitHub org and onboard to Konflux. We only need the org set up and the Konflux GitHub app installed.

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>

• Downstream build process produces all operand images on Konflux.
• Build process for components includes SDL required tasks (Snyk scan, ClamAV, SBOM).
• Basic upstream unit tests are enabled through a CI pipeline. Moving out to a separate 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