-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI should verify that this project can be successfully deployed #61
Comments
My suggestion for this setup would be to use I am not sure this would work for |
Would minikube just use a driverless config and setup the cluster directly on travis? |
It depends on what we're going to use for CI. It's too bad there isn't a
cloud-native CI that will let you test stuff in a kube they create for
you...
For openshift, we can just use `oc cluster up --service-catalog=true` and
go from there.
…On Mon, Feb 26, 2018 at 10:46 AM, Carolyn Van Slyck < ***@***.***> wrote:
Would minikube just use a driverless config and setup the cluster directly
on travis?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAWXmPCAEm-U6JqYtAclfB0kusBF2gh7ks5tYtHIgaJpZM4SRRti>
.
|
That would make my life so much easier. Please take my money. 💰 |
Example setup https://github.com/LiliC/travis-minikube of what I was thinking. More details explained here. |
Ideally, there would be jobs that checked:
The text was updated successfully, but these errors were encountered: