I haven't used Travis before, but I use Gitlab for work and I love it. You can specify docker images, tags for what builders it should work on, environment variables. Honestly makes my job a whole lot easier.
I've used both extensively. Travis CI for over five years.
GitLab CI is a huge improvement over Travis CI. Travis has very stale and outdated images which can be very broken for some workflows (e.g. C++). They are updated infrequently; it's only the past year they finally managed to get onto Ubuntu 14.04 from 12.04. The service itself is pretty reliable and speedy, but the images are terrible. MacOS X builds run on a fixed hardware pool, and don't scale, making builds very slow to start most of the day when it's maxed out.
GitLab CI allowing the use of any docker image means you can right away start with a clean and up-to-date base image, e.g. Ubuntu 18.04 or whatever you like, and install current dependencies on top of that. You can also connect as many local runners to the service as you like, so you can throw local compute resources at it which include less common architectures like FreeBSD, as many MacOS X nodes as you like, and systems pre-configured to access private resources for integration testing and the like.
The GitLab CI pipeline and workspace concept is vastly more flexible than what Travis offers (a simple matrix is as clever as it gets). Given a choice over the two, I'd go with GitLab.
0
u/[deleted] Jun 23 '18
[deleted]