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

Buildpacks BuildStrategy as Dev Preview

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • builds-1.0.1
    • None
    • shipwright
    • None
    • Pipeline Integrations #3246, Pipeline Integrations #3247, Pipeline Integrations #3248, Pipeline Integrations #3249, Pipeline Integrations #3250

      Story (Required)

      As a developer trying to build containers with Shipwright, I want to try the Buildpacks ClusterBuildStrategy (i.e. in Dev-Preview) so that I can quickly build my applications with Shipwright.

      Background (Required)

      Shipwright has an upstream set of example build strategies.
      When we provide Shipwright downstream, we will want to give clear guidance on configuring the clusterBuildStrategy (buildpacks) that is in dev-preview along with the supported strategies.
      We will also want to provide a quick way for customers to install cluster build strategies - for instance, via a single `oc apply` command.

      Out of scope

      • Automate installation of cluster build strategies
      • CI Testing that includes strategies from this catalog

      Approach (Required).

      1. Add Ubi buildpacks strategy (marked as dev preview on docs and other references)
      2. Update upstream documentation (openshift-catalogs) with the steps for installing/configuring cluster build strategies

      Dependencies

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

      Acceptance Criteria (Mandatory)

      • ubi buildpacks strategy listed in the catalog within the redhat-developer/openshift-builds-catalog repository.
      • The strategy has a dedicated README.md file explaining:
        • all the parameters & additional configuration details,
        • Installation instructions,
        • and, a basic example explaining the usage of respective buildStrategy.

      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-asatyam Ayush Satyam
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: