-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
5
-
False
-
None
-
False
-
RHDP-675 - Enable continuous delivery of gitops product and enhancements
-
-
-
GITOPS Sprint 236, GITOPS Sprint 237, GITOPS Sprint 238
Background (Required)
As a maintainer of openshift-gitops, I would like to run kuttl tests and argocd e2e tests automatically before a release goes out (whether it is automated e.g. BOTA or y-stream/z-stream). We only allow a release to go out when all tests pass.
In this story, we will add a gating.yaml file in he root folder of dist-git repo. gating.yaml configures what tests are gating.
Approach (Required)
We will follow the documentation.
We need to add a gating.yaml file in the root folder of our dist-git repo:
# Example gating.yaml file, we may need to polish it.
---
!Policy
# id is optional and can be anything.
id: "gitops-cvp"
product_versions:
- cvp
decision_context: cvp_default
rules:
- !PassingTestCaseRule { test_case_name: gitops-e2e.pipeline.test }
Dependency
https://issues.redhat.com/browse/GITOPS-2801 CVP to trigger Plumbing tests and send results to ResultsDB
Acceptance Criteria (Mandatory)
- Auto-Release flag is set in Comet when the acceptance tests pass.
- Failing tests are reflected in ResultsDB, preventing the release.
Done Checklist
- Code is completed, reviewed, documented, and checked in
- Unit and integration test automation has been delivered and running cleanly in continuous integration/staging/canary environment
- Acceptance criteria are met