Story (Required)

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

As a developer trying to trigger a Shipwright build with an event I want to deploy Shipwright Triggers on my cluster so that I can configure event triggers for my builds.

Background (Required)

<Describes the context or background related to this story>

The Shipwright Triggers project currently does not have a published release on GitHub. Releases make it easy for developers to install on their cluster.

Out of scope

<Defines what is not included in this story>

• Add triggers to the operator - see BUILD-601

Approach (Required)

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

TBD through refinement

Dependencies

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

TBD through refinement

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>

• Shipwright Triggers has a release.yaml on GitHub.
• Artifacts for the Triggers project release conform to upstream standards

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