chore(CICD): list down the pain points associated with CI CD

mayadata-io / d-operators

Declarative patterns to write kubernetes controllers

Apache License 2.0

10 stars 7 forks source link

chore(CICD): list down the pain points associated with CI CD #49

Open AmitKumarDas opened 4 years ago

AmitKumarDas commented 4 years ago

ProblemStatement: As a DevOps admin, I want to list down the pain points associated with litmus scripts. I would like to solve them via tools or enhancing litmus itself. This issue will acts as a tracker for the same.

AmitKumarDas commented 4 years ago

Amit Bhatt  14 minutes ago
For getting logs we need to reproduce the failure again 
so that I can check from the cluster.

Ajesh  14 minutes ago
We need to print log on failures or collect the logs.
These are improvements  @amitd

AmitKumarDas commented 4 years ago

Grabbing pod logs & perhaps uploading them into some Github oep-e2e-results repo
Grabbing pod & custom resource description / yaml & perhaps uploading them into some Github oep-e2e-results repo

AmitKumarDas commented 4 years ago

ProblemStatement: Kubera E2E pipelines are run in more than one Kubernetes clusters. Each pipeline has got its own division of test cases. All these pipelines are managed from a single gitlab instance. As of today, it is difficult to know which tests are run in which Kubernetes cluster. It will be good to provide a declarative specification that determines the clusters to corresponding test cases.