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.
"It is scalable."
"The dashboard and interface make it easy to use."
"Their CI/CD engine is very mature. It's very comprehensive and flexible, and compared to other projects, I believe that GitLab is number one right now from that perspective."
"The solution's service delivery model is fantastic."
"We have seen a couple of merge requests or pull requests raised in GitLab. I see the interface, the way it shows the difference between the two source codes, that it is easy for anyone to do the review and then accept the request; the pull request is the valuable feature."
"CI/CD is very good. The version control system is also good. These are the two features that we use."
"CI/CD and GitLab scanning are the most valuable features."
"Of all available products, it was the easiest to use and easy to install."
"This solution has helped us in automating the build and test process, reducing time."
"The most valuable feature of the solution is its integration between different tools."
"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."
"It can scale easily."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"The initial setup is pretty simple."
"It's very easy to learn."
"Jenkins has excellent task planning features."
"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."
"GitLab could improve the patch repository. It does not have support for Conan patch version regions. Additionally, better support for Kubernetes deployment is needed as part of the package."
"When deploying the solution on cloud and the CI/CD pipeline, we have to define the steps and it becomes confusing."
"Expand features to match other tools such as a static code analysis tool so third-party integrations are not required."
"I'm new to GitLab, so I would appreciate more documentation about the code and commands."
"The integration could be slightly better."
"GitLab could improve by having more plugins and better user-friendliness."
"GitLab can improve by integrating with more tools, such as servers with Docker."
"The bug fix speed is very slow."
"It can be improved by including automated mobile reporting integrations."
"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
"Jenkins could improve the integration with other platforms."
"Jenkins takes a long time to create archive files."
"Some kind of SaaS product would be helpful in providing organizational structure."
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, SonarQube, Bamboo, AWS CodePipeline and Veracode, whereas Jenkins is most compared with Bamboo, AWS CodePipeline, IBM Rational Build Forge, Harness and Tekton. 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.
