Story (Required)

As a developer trying to build my application with Cloud Native Buildpacks I want to build my application by only specifying the "builder" image for my buildpack.

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

As noted in BUILD-1654, the buildpacks strategy requires developers to set the buildpack builder and runtime images. These need to be "aligned" - most builder images have an associated set of supported runtime images.

This does not appear to be a hard requirement for other buildpack builders. The pack CLI and upstream Tekton buildpack tasks do not require the runtime image to be set. it appears that metadata within the builder image determines the "default" runtime image.

See https://buildpacks.io/docs/for-platform-operators/how-to/integrate-ci/tekton/

Out of scope

<Defines what is not included in this story>

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

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

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>

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