Story (Required)

As a developer trying to build container images with Shipwright I want Builds for OpenShift to deploy Shipwright v0.14.0

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

Upstream operator will release v0.14.0 (see BUILD-1170). We need to update the downstream operator to deploy the same version, using our downstream bits.

Out of scope

<Defines what is not included in this story>

TBD

Approach (Required)

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

• Bump shipwright-io/operator dependencies to v0.14.0 and update build `release.yaml` with new version
• Build operator container image
• Update bundle to use new operator image. If using `main` branch, okay to have operator deploy upstream operand images.

Dependencies

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

• Upstream operator release - BUILD-1170

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>

• Builds Operator uses Shipwright v0.14.0 operator code as library
• Operator deploys Shipwright Build v0.14.0 controllers, CRDs, etc. (upstream images acceptable).

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