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

Make shp CLI available on mirror.openshift.com

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • builds-1.0
    • shipwright
    • None
    • 3
    • True
    • Hide
      Waiting on the following:
      * ART-9166
      * CLOUDDST-22161
      * CLOUDDST-22397
      Show
      Waiting on the following: * ART-9166 * CLOUDDST-22161 * CLOUDDST-22397
    • False
    • SECFLOWOTL-160 - Release Builds 1.1
    • 3
    • Pipeline Integrations #3253, Pipeline Integrations #3254

      Story (Required)

      As a developer trying to manage builds & buildRuns via shp, I want to have easier access to the shp binary.

      Background (Required)

      Currently, the shp CLI is being shipped only as rpm. Having shp CLI shipped as a binary will help with easier download & usage.

      Out of scope

      • Making shp CLI binary available on OpenShift console.
      • Making shp CLI binary container image available.

      Approach (Required)

      • Update the version to 0.12.0 in midstream, & trigger the openshift-builds-client build.
      • Reach out to RCM team as they can help to generate binaries. Use GChat space "SP-Cloud" for this.
      • Reach out to ART team to publish those binaries from this internal link to mirrors. Use Slack, #forum-ocp-art

      Dependencies

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

      • shp CLI v0.12.0 tagged on GitHub upstream

      Acceptance Criteria (Mandatory)

      • The shp binaries are available on mirror.openshift.com.
      • Binaries are available for the following OS and architectures:
        • linux/amd64 (aka x86_64)
        • windows/amd64
        • darwin/amd64 (macOS Intel)
      • Documentation is updated with the location for shp cli.

      Open questions:

      • Do we need to ship power/z for Linux?
      • Testing of the CLI - do we need QE verification on all os/arch combinations?

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      • Engineering: 3
      • Docs: 1
      • QE: 2

      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
              rh-ee-apjagtap Apoorva Jagtap
              Divyanshu Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: