Hacker News Reader

Gitlab has great built in support for CI [0], and you can easily add and run your own CI runners [1].

[0]: https://docs.gitlab.com/ce/ci/README.html

[1]: https://docs.gitlab.com/ce/ci/runners/README.html

GitLab's built-in CI is very good, and simpler than Travis for some things.

You also have the option (unlike Travis) of registering your own runners in your project settings, and you can do this either on gitlab.com or another deployment, without needing to be an admin of the deployment - you can get a key for it in your own project's settings. I'm using this at work, where we have an internal GitLab that I'm not an admin of (and where the GitLab admins probably have no interest in running a CI system), to do a small bit of CI on some things using one of my team's servers as a runner.

We use gitlab's built-in runners and pipelines for continuous deployment to kubernetes and it works very well. We self-host our repos but the same tools are available through the hosted version.