[We&#x27;re running a Gitlab instance and one CI instance with multiple CI runners in the Google Cloud.]<p>Gitlab CI is great if you don&#x27;t need dynamically provisioned build slaves, for which I found no integrated support. In general, Gitlab CI is <i>much</i> more straightforward and easy to use than Jenkins.<p>Jenkins wins when it comes to stuff like build artifacts (getting these out of Jenkins is easy peasy (just wget them and provide basic HTTP auth if needed), but with GitLab I have not yet found a way to automatically download say the latest build results), credentials management and other &quot;more enterprisey&quot; features.<p>Jenkins is easy to install on Debian-based systems; I have no real experience in setting up Gitlab other than via the official Docker images, which is nearly as easy as typing `apt-get install jenkins`. Setting up CI runners&#x2F;instances is easy as well (apt-get install + one or two calls to gitlab-multi-runner).<p>Overall I&#x27;m pretty happy with Gitlab CI. Especially the fact that every developer in our company can take advantage of automated builds by just enabling CI support and putting a .gitlab-ci.yml in the repository is great. Over are the days were admins had to manage Jenkins jobs.