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

Document sample running buildah build

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • builds-1.0
    • None
    • shipwright
    • None
    • Pipeline Integrations #3245, Pipeline Integrations #3247
    • 2

      Story (Required)

      As a user trying to run a buildah build on openshift, I want to find a technical detailed documentation listing the steps to do s

      Background (Required)

      Openshift builds offers the capability of building images using buildah throught buildah strategy,
      To make onboarding to openshift-builds easier and  enhance the user experience around openshift-builds, we need to document real user use cases.

      Out of scope

      • Document openshift-builds installation: samples documentation should assume a running openshift cluster with openshift-builds installed
      • Document troubelshooting any issue related to installtion or a running openshift builds controller

      Approach (Required)

      • Withing a running openshift cluster and installed build controller
      • Document and install buildah strategy
      • Create and document a build object
      • Create and document a buildrun object
      • Show the resulting image

      Dependencies

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

      Acceptance Criteria (Mandatory)

      • A google docs documentation created with detailed steps on how to run buildah build using openshift-builds

      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-apjagtap Apoorva Jagtap (Inactive)
              jkhelil abdeljawed khelil
              Shipra Singh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: