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

SourceBuildStrategy Type Migration

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • shipwright
    • None
    • Builds Sprint #35, Builds Sprint #36
    • 2

      Story (Required)

      After successful demo of POC by Jason, I want to continue to dig into various specs of Build Config and attempt to build on the POC to accommodate various examples of migration involving other fields from the spec. This story covers SourceBuildStrategy Type in BuildConfig Specs which defines the core fields of source strategy 

      Outcomes Expected:

      • Additional Code including tests for SourceBuildStrategy Type
      • Create RFEs for what additional feature to be supported

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

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

      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>

      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

              rh-ee-prathore Prateek Rathore
              rh-ee-prathore Prateek Rathore
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: