Re:Introducing zero-configuration GitLab CI
by geerlingguy on Monday July 07, 2014 @09:44AM
(#7998740)
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...
[ Parent
| on HN ]
GitLab CI integrates directly with GitLab CE installs, requiring no configuration from the end user. Compared to Jenkins, it will automatically link up with your repo and start builds on commits and pull requests. These are things you have to manually configure with something like Jenkins. As for Travis CI, the integration is just as seamless. GitLab CI talks to GitLab installs via the CE api and automatically pulls in your projects, sets the build status on your repos and assigns runners to perform your builds. The GitLab team has really done an amazing job building a CI offering that integrates really well with their CE repo app.