Story (Required)

As a microshift release engineer, trying to build and release microshift ISO image with MicroShift, I want the microshift-gitops rpms to be located in a centrally accessible location, so that the microshift CI build process can pick up those rpms from the well defined location.

Background (Required)

MicroShift ISO images are built using the image-builder. It can take in a directory containing the microshift-rpms and also can take in additional rpms with the argument -custom_rpms argument. Since microshift-gitops is not tied to the underlying OCP version and acts like a standalone product, we build the rpms using the existing CPaaS build infrastructure. This would then be integrated to the CI build system of MicroShift to build the final ISO image.

Out of scope

None

Approach (Required)

Upload the RPMs to the S3 bucket on which the mirror.openshift.com is accessing the storage.

Dependencies

None

Acceptance Criteria (Mandatory)

• The rpms are available in mirror.openshift.com in an appropriate directory structure.

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