-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
Story (Required)
As a Konflux user, I would like to build the component through Konflux.
Background (Required)
- All the Red Hat products have to onboard on to Konflux by end of the year.
Out of scope
- Any other component
Approach (Required)
- Onboard the GitHub repo for the must-gather component on to the Konflux.
- Use one of the Docker build executors to get the component built.
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
- Onboard the GitHub repo for the must-gather component on to the Konflux.
- Use one of the Docker build executors to get the component built.
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
- clones
-
GITOPS-5465 Build Argo CD component through Konflux
-
- Closed
-
- is cloned by
-
GITOPS-5467 Build kam delivery component through Konflux
-
- Closed
-
-
GITOPS-5882 Build gitops operator component through Konflux
-
- Closed
-