Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1170

Update Shipwright Operator to deploy Builds 0.14

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • shipwright
    • False
    • None
    • False
    • Release Note Not Required

      Story (Required)

      As a developer trying to deploy Shipwright I want the operator to deploy Builds v0.14

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

      We need the upstream Shipwright operator to deploy Builds v0.14.

      Out of scope

      <Defines what is not included in this story>

      • Releasing the Shipwright operator upstream with v0.14.x
      • Enhance the operator to run the CRD migrator job.

      Approach (Required)

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

      1. Update `release.yaml` and the build samples manifest(s) to v0.14
      2. Address any "breaking" changes that may impact upgrade. For example, removal/rename of a deployed component.
      3. Verify that builds behave correctly (smoke test)
      4. Submit and merge PR upstream.

      Dependencies

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

      • Builds v0.14 release candidate upstream

      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 operator deploys v0.14.0
      • Shipwright can be upgraded from v0.13.0 to v0.14.0

      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

              Unassigned Unassigned
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: