We used both at previous and current job. As far as I'm concerned there's no reason to stick to Jenkins unless you really can't afford time to migrate. And even

We used both at previous and current job. As far as I'm concerned there's no reason to stick to Jenkins unless you really can't afford time to migrate. And even then you probably should. Main differences: - GL is waaaay easier to setup and maintain, both initially (installation, configuration and upgrades) and especially when configuring runners and per-project tasks - GL saves information about tasks in a file which is part of repo. This might seem counter-intuitive at first, but it makes sense when you realise that build process depends on version (if you want to be able to build old versions of your products). Also, this way config is part of source repo so backup is easier. - Jenkins can do anything - with a proper plugin. Hunting for the right plugins however is a neverending story. God forbid you ever have to reinstall Jenkins... Of course that's just my experience. Until GitLab came along we have used Jenkins for a few years and... well, it worked. But it's UX is not comparable to GitLab's.