Jenkins vs GitLab CI
No installation needed
GitLab CI ships with GitLab and is ready to use out of the box.
Minimal build configuration
GitLab CI requires less configuration for your builds than a similar Jenkins setup.
Both GitLab CI and Jenkins are extensible through an API or plugin system but GitLab's core CI feature set is more comprehensive than Jenkins.
Built for containers and Docker
GitLab ships with its own Docker container registry, Docker CI Runner and is ready for a complete CI/CD container workflow, while Jenkins requires you to install, configure and maintain additional plugins to create a similar workflow.
GitLab CI/CD is Cloud Native, purpose built for the cloud model. GitLab ships with Red Hat OpenShift and Kubernetes support out of the box.'
Container debugging on any environment
Easily debug your containers in any of your environments using the built-in GitLab Web Terminal.
GitLab ships with Prometheous allowing you to monitor the performance of your deployed environments without any addtional setup.
Integrates with Cycle Analytics
GitLab CI integrates with GitLab Cycle Analytics allowing you see how much of your cycle time from idea to production is spent on development, testing and review.
Last updated: March 17, 2017 Download as PDF
Since GitLab fans wrote most of the text here there is a pro-GitLab bias. Nonetheless we try hard to ensure the comparisons are fair and factual. Please also add things that are great in other products but missing in GitLab. If you find something that is invalid, biased, missing, or out of date in the comparisons, please open a merge request for this website to correct it. As with all the pages on this website you can find where this page lives in the repository via the link in the footer.