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

Make shp CLI available on OpenShift console

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • SECFLOWOTL-28 - Openshift Builds in clusters with restricted networks
    • Enhancement
    • 5
    • Builds Sprint #15, Builds Sprint #16, Builds Sprint #17

      Story (Required)

      As a developer/customer trying to manage builds & buildRuns via builds operator using 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 mirror.openshift.com.
      • Making shp CLI binary container image available.

      Approach (Required)

      • Once the binary is available on mirror.openshift.com(or now, content gateway), work with the OCM UI team to get the same binary available on console.redhat.com/openshift/downloads
      • Create an issue similar to OCMUI-1489 to request the changes for linking the binary on content gateway to console.redhat.com.

      Dependencies

      Acceptance Criteria (Mandatory)

      • The shp binaries are available on console.redhat.com/openshift/downloads.
      • 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 details/examples on accessing shp from console.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

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

      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
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: