Introducing zero-configuration GitLab CI

GitLab B.V. CEO here, we think GitHost.IO has done a wonderful job to make it very easy to set up a CI solution for organizations. I've tested it and was able to set up a coordinator with a couple of runners in 5 minutes. This is a really cost effective way to test multiple pull/merge requests in parallel. I'll be in this thread for a few hours.

I've used GitLab a bit, and it seems to be a pretty simple self-hosted imitation of GitHub that does 99% of what I need to do for team code hosting. How does GitLab CI compare to Travis CI? Is it as flexible and seamless as Travis' GitHub integration? Right now I mostly use Jenkins, but more than half my projects could conceivably be run through something like Travis with minimal changes...

I&#x27;m interested in knowing how GitHost are hosting GitLab CI. I&#x27;m currently using GLCI to run integration tests in Vagrant VMs, which unfortunately means most &quot;cloud&quot; hosting is out.<p>joshfng (Assuming you are from GitHost). Do you know if your environment would support this?

A pretty cool service for Gitlab CI, when will they add https support?