Explore CI/CD using Docker machines with Jenkins
Opened this issue · 2 comments
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
What happened:
For some linux distributions getting a vagrant variant might be difficult as some of them have moved to doing it more in the docker way. It makes sense if the CI/CD setup had an integration with docker machines too the same way it has for vagrant.
What you expected to happen:
If a viable vagrant option for a particular linux distribution then we can have a docker machine implementation to run the CI.
How to reproduce it (as minimally and precisely as possible):
This is a feature request.
Anything else we need to know?:
Environment:
- kubectl get nodes
- kubectl get pods --all-namespaces
- kubectl get services
- kubectl get sc
- kubectl get pv
- kubectl get pvc
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a
): - Install tools:
- Others:
We could use the argo project's CI-CD workflow and notes as reference for this : https://blog.argoproj.io/argo-workflow-demo-at-the-kubernetes-community-meeting-c428c3c93f9d,
i.e., not jenkins specifically but CI-CD in general with dockers.
Moving this to openebs/e2e-infra project.