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

Automated Install of supported build strategies via the upstream operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done-Errata
    • Icon: Major Major
    • builds-1.0
    • None
    • shipwright
    • None
    • Upstream
    • 3
    • False
    • None
    • False
    • Pipeline Integrations #3247
    • 1

      Story (Required)

      As a developer trying to build applications with Openshift-builds I want the operator to install the supported build strategies (buildah and s2i) so that I can quickly get started building applications.

      Background (Required)

      The upstream Shipwright operator currently does not install or reconcile ClusterBuildStrategies.

      Out of scope

      <Defines what is not included in this story>

      • Install our downstream, Red Hat supported cluster build strategies. See BUILD-772
      • Upstream support/definition of "catalogs"

      Approach (Required)

      The upstream Shipwright operator currently does not install or reconcile ClusterBuildStrategies.
      We have a fast path to have the downstream operator installing the redhat supported strategies: buildah and s2i. The downstream operator will install buildah and s2i strategies as part of openshift-builds component (in kodata/release.yaml) Downstream work will be done in BUILD-772

      Dependencies

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

      None

      Acceptance Criteria (Mandatory)

      -buildah and s2i strategies installed via the openshift-builds operator
      strategies can be found here https://github.com/redhat-developer/openshift-builds-catalog-

      Upstream build strategies are deployed via upstream Shipwright operator.

      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
              jkhelil abdeljawed khelil
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: