Story (Required)

As a developer trying to build applications with Shipwright I want a video demonstration of how to use Shipwright.

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

Developers and CEE need more than just docs to learn how to use Shipwright/Builds for OpenShift. A recorded demo can help.

This will be presented at OpenShift Commons on April 3rd. It is meant to be a re-introduction of Shipwright using the Builds for OpenShift operator.

Out of scope

<Defines what is not included in this story>

• Demo emerging/upcoming features

Approach (Required)

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

• Showcase install process (install OpenShift Pipelines, then Builds for OpenShift)
• Use shp CLI to build a "hello world" application two (or three) ways:
  • Use Containerfile and buildah
  • Use s2i
  • Use paketo buildpacks
• Speed up the build with build caching

Dependencies

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

• Operator available on OperatorHub for the demoed OCP version (4.14 or 4.15)

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>

• Video demo which uses the shp CLI
  • Run an s2i build
  • Run a buildah build
  • Stretch goal - build with buildpacks

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

Notes

Demo to be presented at OpenShift Commons in April