Story (Required)

As a Shipwright contributor trying to support multi-arch builds I want Shipwright to optionally use PipelineRuns to execute a build pipeline.

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

Multi-arch builds require builds to execute in a PipelineRun so the individual container image builds can run in parallel. This requires the main BuildRun controller to be refactored, since it currently runs builds in a single TaskRun.

Out of scope

<Defines what is not included in this story>

• Run multi-arch container builds
• Refactors unrelated to running the build in a PipelineRun

Approach (Required)

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

Dependencies

• Encapsulate TaskRun in an Interface: BUILD-1486

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 can successfully execute using a PipelineRun
• Use of a PipelineRun is gated behind an environment variable or feature flag and is disabled by default.
• The PipelineRun should execute as at least two TaskRuns (potentially 3):
  • Obtain Source
  • Build Container
  • Push Image
• The PipelineRun version of the build should be feature-compatible with the TaskRun version.

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