2 ms·
So I use Gitlab CI on my personal projects, and in work I was "the Jenkins guy" on our team for a good while, though I've since changed projects to one using an
by Macha 9y ago
So I use Gitlab CI on my personal projects, and in work I was "the Jenkins guy" on our team for a good while, though I've since changed projects to one using an internal tool so my Jenkins knowledge is ~1yr outdated.
Gitlab CI:
==========
+ No infrastructure required. I like to work on my private projects and not their servers.
+ Mostly-declarative syntax with a easy way out when required. Jenkins until recently only had imperative options (scripts in a UI/scripts in classic Pipeline)
+ Caching between builds is inbuilt, while in the past we had to roll our own with Jenkins
- No easy way to share the same script between repos without copy/pasting your .gitlab-ci.yml.
Jenkins:
========
+ More options to display output. Need to have your tests list which ones passed and which failed? Done.
+ Credential Management is better, at least at the "early adopter" free tier I'm on for Gitlab.
- The Legacy/Default UI is bad. The Blue Ocean UI is a bad UI in a winamp skin.
- Integrating plugins designed with pre-workflow jenkins in mind to Jenkins Pipeline is a bit awkward, often requiring you to know which class is used internally in the plugin.
- sytse 9y agoThanks for reviewing GitLab. We introduced a way to share scripts in the last version as a paid feature https://about.gitlab.com/2018/02/22/gitlab-10-5-released/#include-external-files-in-cicd-pipeline-definition https://about.gitlab.com/2018/02/22/gitlab-10-5-released/#in...