3 ms·
That's exactly my experience. I used the docker omnibus containers to get quickly up and running. Running, supervising and updating is a pleasure in combination
by cedricziel 10y ago
That's exactly my experience. I used the docker omnibus containers to get quickly up and running. Running, supervising and updating is a pleasure in combination with docker-compose.
As for CI, I utilized the docker-machine runner so we could autoscale based on demand.
Big plus: With Google Cloud Platform, we can leverage preemptible VMs for the runners (not for the coordinator of course), so the cost is really low.
- sytse 10y agoAwesome, if you're using Google Cloud you'll be happy to hear that we just merged Kubernetes support for Runner creation https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/30 https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_r... Giving you the option to use Google Container engine to spin up new Runners.
- HorizonXP 10y agoThis is awesome! Our whole stack runs on Kubernetes, so this kind of integration is very welcome!
- sytse 10y agoGlad to hear that. And many thanks to James Munnelly for being patients with me and the rest of our team over the period of a year to get this done.
- swozey 10y agoThis is fantastic. Right now I use GCE autoscaling groups to spin up runners while I've got several kubernetes clusters running 24/7. It'll be nice to utilize those for builds (especially with how fast the scheduler is) going forward. Saves money, as well.
- sytse 10y agoAwesome, glad to hear you can make use of this.