Story (Required)

As a developer I want to maintain the build pipeline in single repository as single source of truth.

Background (Required)

Currently we are using the same build pipeline for all the container of Builds for Openshift and the same FBC pipeline for different OCP version, but we are keeping the pipeline definition in all the repo. This makes is difficult to maintain the pipeline updates for individual repo.

Out of scope

Approach (Required)

• Create a repo for all the pipelines and tasks
• Update the PipelineRun in all the repos (shiwright-io, operator, catalog, s2i, shared-resources) to refer to this build pipeline.
• Onboard the pipeline repo to konflux, so that mintmaker can update the references periodically.

Reference: https://konflux-ci.dev/docs/how-tos/workflows/keep-remote-pipelines-up-to-date

Dependencies

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

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

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