Epic Goal

Refactor Shipwright's build logic to execute builds in a Tekton PipelineRun. This is a necessary prerequisite to fanning out parallell multi-arch builds.

Why is this important?

OpenShift supports multi-arch compute clusters where worker nodes with different architectures (e.g. x86, Arm) are available within a single cluster. Building applications for multiple architectures allows customers to make deployment decisions based on economics and efficiency criteria.

Shipwright currently assumes all builds run in a single TaskRun with sequential build steps. To run multi-arch builds, we first need to refactor Shipwright's codebase so it can execute builds as a multi-step PipelineRun.

Acceptance Criteria (Mandatory)

• Shipwright builds can run in a PipelineRun with an appropriate feature flag enabled.
• The image produced by the PipelineRun be reasonably equivalent to an image produced by a build using TaskRuns.
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment