Story (Required)

As a developer trying to build containers with Shipwright I want to build images using Shipwright v0.14 so that I can take advantage of the latest upstream features.

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

Shipwright community release v0.14.0 in November 2024. For builds-1.3 we are going to rebase our downstream Shipwright components to align with this version.

Out of scope

<Defines what is not included in this story>

• Bump downstream operator - will be done in BUILD-1204 (potentially as a prerequisite)
• CLI release - will be done in BUILD-1209

Approach (Required)

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

• Sync `release-v0.14` branch from upstream into our fork
• Create `builds-1.3` branch in our fork from release-v0.14
• Onboard `builds-1.3` branch to Konflux (copy Containerfile/Dockerfiles, create new application from project controller template).
• Assemble Shipwright controller images on Konflux
• Bump operator (bundle) to deploy downstream Shipwright images.

Dependencies

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

• BUILD-1204

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 deploys downstream Shipwright operands, based on 0.14 upstream
• QE testing passes for buildah, s2i build strategies

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