-
Story
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
3
-
blocked by https://issues.redhat.com/browse/GITOPS-2579
-
False
-
-
-
GITOPS Sprint 232, GITOPS Sprint 236, GITOPS Sprint 237, GITOPS Sprint 238
Story (Required)
As a contributor to the gitops-must-gather repo, I want my PR to go through CI to check that will test my code and identify any errors with it.
Background (Required)
Currently the only CI check that runs when a contributor submits a PR is a DCO check. __
Out of scope
Changing the functionality of the gitops-must-gather.
Approach (Required)
Add ci-operator to the gitops-must-gather repo (an example of how this is done for a repo like kam can be found here) . Unit/e2e tests should already be added as part of GITOPS-2579, so you should be able to tell openshift-ci to run these tests.
Dependencies
Acceptance Criteria (Mandatory)
- Make a PR to add CI for gitops-must-gather here
- Add step to run all unit/e2e tests that exist in gitops-must-gather
- Add a lint check to identify any linter errors
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