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

Create shared GitHub workflow for release branching

XMLWordPrintable

    • 1
    • Pipeline Integrations #3254

      Story (Required)

      As a Shipwright maintainer trying to release z-streams I want a shared release branching workflow that I can use across repos.

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

      Create a shared GitHub workflow and starter workflow template so Shipwright repositories can quickly create release branches. The repos that actually release code can create the "real" GitHub Action workflows from the starter template.

      Out of scope

      <Defines what is not included in this story>

      • Implement the release branch workflow in Shipwright code repos (build, operator, cli)

      Approach (Required)

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

      See SHIP-0038

      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>

      • Shared release branch workflow is created and merged upstream.
      • At least one Shipwright repo (build, cli, etc.) is able to use it.

      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

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

              Created:
              Updated:
              Resolved: