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.
"Everything is easy to configure and easy to work with."
"It speeds up our development, it's faster, safer, and more convenient."
"CI/CD is very good. The version control system is also good. These are the two features that we use."
"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."
"I have found the most valuable feature is security control. I also like the branching and cloning software."
"GitLab's best features are maintenance, branch integration, and development infrastructure."
"The merging feature makes it easy later on for the deployment."
"We like that we can have an all-encompassing product and don't have to implement different solutions."
"There are a large number of plugins available for integration with third party systems."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"I like that you can find a wide range of plugins for Jenkins."
"A lot of support material exists via a single web search of exactly what you're looking for."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"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."
"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."
"The initial setup is simple."
"It could have more security integrations and the ability to check the vulnerability of the code. I don't think it is a responsibility of Gitlab, but it would be nice to have more options to integrate with."
"GitLab could improve by having more plugins and better user-friendliness."
"The price of GitLab could improve, it is high."
"The documentation is confusing."
"There was a problem with the build environment when we were looking at developing iOS applications. iOS build require Mac machines and there are no Mac machines provided by GitLab in their cloud. So to build for mobile iOS application, we needed to use our own Mac machine within our own infrastructure. If GitLab were to provide a feature such that an iOS application could also be built through GitLab directly, that would be great."
"It should be used by a larger number of people. They should raise awareness."
"Even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still."
"The solution does not have many built-in functions or variables so scripting is required."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"A more user-friendly UI for creating pipelines would be helpful."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."
"Sometimes you have Jenkins restarting because of OOM errors."
"Jenkins needs a faster deployment process."
"There is no way for the cloud repositories to trigger Jenkins."
"Jenkins takes a long time to create archive files."
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.
