-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
-
Story (Required)
As a user trying to setup CICD I want to nteract with ArgoCD ( OpenShift-GitOps ) from Tekton ( OpenShift-Pipelines)
Background (Required)
We have frequent questions from our users on how to integrate Argo with Tekton.
We need to haveĀ a tried and tested guide on the steps to be followed in docs.openshift.com.
There is blog available which can be used as reference
https://demo.openshift.com/en/latest/gitops-with-cicd/
https://cloud.redhat.com/blog/from-code-to-production-with-gitops
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
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