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.
"This product is always evolving, and they listen to the customers."
"It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience."
"Everything is easy to configure and easy to work with."
"The most valuable feature of GitLab is the ability to upload scripts and make changes when needed and then reupload them. Additionally, the solution is user-friendly."
"We use the Git repository and tagging feature. We are a product-based company and use this solution to move to a forward or backward tag."
"The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline."
"It scales well."
"The dashboard and interface make it easy to use."
"There are a large number of plugins available for integration with third party systems."
"It has a lot of community posts and support."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"Jenkins is very stable."
"The initial setup is simple."
"I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities."
"I would like to see better integration with project management tools such as Jira."
"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."
"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."
"We would like to generate document pages from the sources."
"I used Spring Cloud config and to connect that to GitLab was so hard."
"We do face issues in our company when we run out of disk space."
"As a partner, sometimes it's difficult to get support. They have a really complicated procedure for their support."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
"A more user-friendly UI for creating pipelines would be helpful."
"The learning curve is quite steep at the moment."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"Jenkins needs a faster deployment process."
"It could be cheaper."
"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
"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."
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.
