OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• Run Shipwright Builds as a task within a Tekton Pipeline

Why is this important?

• Building a container image is often one step in an application delivery pipeline.
• Development teams may want to do other tasks in parallel with the build of a container image in their pipeline (static code analysis, unit testing, linting, etc.)
• After the container image is built, integration/e2e tests may want to be run in a simulated environment using the candidate image.
• Other steps/tasks may need to be run against the candidate image in a delivery pipeline, such as generation of SBOMs and vulnerability scanning.

Scenarios

1. Build a container image with Shipwright as part of a Tekton pipeline
2. Run unit tests in parallel with container image builds
3. Run a vulnerability scan against an image from a Shipwright build

Acceptance Criteria

• 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

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>