GitLab Master Plan

Re:GitLab Master Plan by cedricziel on Tuesday September 13, 2016 @11:11AM (#12488949)

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.

[ Parent | on HN ]

Re:GitLab Master Plan by sytse on Tuesday September 13, 2016 @11:15AM (#12488981)

Awesome, 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_r... Giving you the option to use Google Container engine to spin up new Runners.

[ Parent | on HN ]

Re:GitLab Master Plan by swozey on Tuesday September 13, 2016 @03:36PM (#12491497)

This 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.

[ Parent | on HN ]

Re:GitLab Master Plan by sytse on Tuesday September 13, 2016 @08:52PM (#12493495)

Awesome, glad to hear you can make use of this.

[ Parent | on HN ]

Re:GitLab Master Plan by HorizonXP on Tuesday September 13, 2016 @12:14PM (#12489631)

This is awesome! Our whole stack runs on Kubernetes, so this kind of integration is very welcome!

[ Parent | on HN ]

Re:GitLab Master Plan by sytse on Tuesday September 13, 2016 @08:44PM (#12493462)

Glad 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.

[ Parent | on HN ]