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

SPIKE: Build Operator with Konflux

XMLWordPrintable

    • 3
    • False
    • None
    • False
    • SECFLOWOTL-27 - Shared Resource CSI Driver GA
    • 3
    • Pipeline Integrations #3254

      Story (Required)

      As a Red Hat Engineer trying to build and release a layered product I want to build my operator on Konflux.

      Background (Required)

      Konflux is the future software factory for Red Hat. We need to investigate its current capabilities for building and releasing operators. What can it do? What experiences are manual/painful?

      Out of scope

      • Konflux onboarding formalities
      • Creating CI pipelines in Konflux

      Approach (Required)

      Investigate the capabilities and Konflux platform and document the gaps compared to the current cPaaS build process for Openshift build operator.
      Find out how to onboard Red Hat products to Konflux.

      The process is documented here.

      Onboarding Red Hat Products to Konflux

       

      Dependencies

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

      Acceptance Criteria (Mandatory)

      • A document should define the gaps between Konflux capabilities and the features required to build Openshift build operator.
      • Figure which teams/channels are responsible for onboarding support
      • Define the pre-requisite for onboarding to Konfluc platform

      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-sabiswas Sayan Biswas
              adkaplan@redhat.com Adam Kaplan
              Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: