We performed a comparison between Jenkins and Gitlab based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Based on the parameters we compared, GitLab comes out ahead of Jenkins. Our reviewers found that installation on Windows is not intuitive and its maintenance can be more demanding.
"The most valuable feature of GitLab is the automatic merging of code."
"The most valuable functionality of GitLab, for me, is the DevOps. Besides the normal source control based on Git, I find the Auto DevOps features most important in the solution."
"GitLab is very well-organized and easy to use. Also, it offers most features that customers need."
"The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline."
"We like that we can have an all-encompassing product and don't have to implement different solutions."
"The best thing is that as the developers work on separate tasks, all of the code goes there and the other team members don't have to wait on each other to finish."
"The most important features of GitLab for us are issue management and all the CI/CD tools. Another aspect that I love about GitLab is the UI."
"The solution makes the CI/CD pipelines easy to execute."
"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."
"Jenkins has been instrumental in automating our build and deployment processes."
"The automated elements are easy to use and you can put them into your server."
"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."
"GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."
"It's very useful when you want to automate different processes from beginning to end."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
"The most valuable feature is its ability to connect with different tools and technologies."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"The solution does not have many built-in functions or variables so scripting is required."
"The integration could be slightly better."
"I rate the support from GitLab a four out of five."
"For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"We would like to generate document pages from the sources."
"GitLab could add a plugin to integrate with Kubernetes stuff."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."
"The user interface could be updated a little."
"The solution could improve by having more advanced integrations."
"The documentation on plugin development could be better: more examples. "
"It would be helpful if they had a bit more interactive UI."
"Logging could be improved to offer a clearer view."
GitLab is ranked 1st in Build Automation with 70 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. GitLab is rated 8.6, while Jenkins is rated 8.0. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". GitLab is most compared with Microsoft Azure DevOps, Bamboo, AWS CodePipeline, SonarQube and GitHub CoPilot, whereas Jenkins is most compared with Bamboo, AWS CodePipeline, IBM Rational Build Forge, Tekton and Harness. See our GitLab vs. Jenkins report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
