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

Install Shipwright Build Strategies via Operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • shipwright

      Story (Required)

      As a developer trying to build appications with Shipwright I want the operator to install a set of curated ClusterBuildStrategies so that I can quickly get started building applications.

      Background (Required)

      The Shipwright operator currently does not install or reconcile ClusterBuildStrategies. Installing a set of cluster build strategies would benefit developers who want to start quickly with Shipwright.

      Out of scope

      • Curation of the list of ClusterBuildStrategies (see BUILD-690)
      • Catalogs for Shipwright build strategies - see BUILD-743

      Approach (Required)

      • Shipwright operator copies a set of cluster build strategies into its repopsitory. Upstream, this is sourced from the samples in GitHub
      • Operator is enhanced to install the cluster build strategies stored in a well-known directory. This may require some refactoring since the build CRDs need to be deployed before the operator attempts to install the cluster build strategies.
      • When downstreaming, we replace the content in the well-known location above with the cluster build strategies we support.

      Dependencies

      1. Upstream source of "community-supported" build strategies
      2. Manifestival library support for installing YAML manifests from a directory

      Acceptance Criteria (Mandatory)

      • Upstream operator is able to install a set of cluster build strategies
      • Downstream version of the operator is able to install our Red Hat-supported cluster build strategies

      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

              jkhelil abdeljawed khelil
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: