Cancel
You must select at least 2 products to compare!
GitLab Logo
9,551 views|7,786 comparisons
98% willing to recommend
Jenkins Logo
6,756 views|5,825 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary
Updated on Mar 30, 2023

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.

  • Ease of Deployment: For Jenkins, the initial configuration with Kubernetes can be clunky and requires third-party plugins. Maintenance is minimal. Installation on Windows is simple but not intuitive. GitLab's initial deployment is straightforward with clear fundamentals, and adoption requires education but is easy to implement.
  • Features: The most valuable aspect of Jenkins is pipeline customization, environment variables for flexible deployment, and seamless GitHub integration. GitLab provides a single platform for all activities including source code, build, test, and deployment management, with an established upgrade roadmap for the next few years.
  • Pricing: Jenkins offers a free, open-source version without specific support needs. Its licensing is renewed annually, and pricing is reasonable. GitLab offers three editions: free, premium, and ultimate, with a steeper price difference between premium and ultimate. GitLab does not have hidden costs.
  • Service and Support: For Jenkins, community support is extensive with a rich knowledge base. Technical support takes 24-48 hours to resolve issues. GitLab's customer service is helpful and responsive with a high rating.

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.

To learn more, read our detailed GitLab vs. Jenkins Report (Updated: May 2024).
771,212 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The SaaS setup is impressive, and it has DAST solutioning.""The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good.""GitLab's best features are maintenance, branch integration, and development infrastructure.""For us, Gitlab's most valuable feature is the integration with Cypress. We're using Cypress as an automation tool, so we're using GitLab as a tool for running in parallel.""GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos.""The most valuable features of Gitlab are integration with CIE and the ability to rapidly deploy solutions, projects, and applications. It is very easy to use, and there are no complaints.""I have had no problem with the stability of the solution.""Key features allow creation of well-presented Wiki that includes ideas, development, and domains."

More GitLab Pros →

"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent.""Jenkins's open-based framework is very valuable.""The solution is scalable and has a large number of plugins that can help you scale it to your needs.""Has enabled full automation of the company.""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.""Having builds and test tasks triggered on commit helps not to break the product.""Jenkins has a lot of built-in packages and tools.""We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."

More Jenkins Pros →

Cons
"There is room for improvement in GitLab Agents.""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.""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.""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.""I'm new to GitLab, so I would appreciate more documentation about the code and commands.""There is a need to improve or adopt AI into the ecosystem like a co-pilot, which Microsoft has done with GitHub.""It is a little complex to set up the pipelines within the solution.""GitLab's UI could be improved."

More GitLab Cons →

"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins.""Sometimes you have Jenkins restarting because of OOM errors.""The solution could improve by having more advanced integrations.""There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided.""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 needs a faster deployment process.""Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams.""It does not have a very user-friendly interface."

More Jenkins Cons →

Pricing and Cost Advice
  • "I think that we pay approximately $100 USD per month."
  • "The price is okay."
  • "It seems reasonable. Our IT team manages the licenses."
  • "Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."
  • "It is very expensive. We can't bear it now, and we have to find another solution. We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year."
  • "I don't mind the price because I use the free version."
  • "We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."
  • "The price of GitLab could be better, it is expensive."
  • More GitLab Pricing and Cost Advice →

  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    771,212 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently.
    Top Answer:For small-scale usage, GitLab offers a free tier. For enterprise pricing, GitLab is more expensive than GitHub, as it's not as widely adopted. GitLab is the preferred choice for many developers… more »
    Top Answer:I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities. Better integration and usability within the pipeline could make a significant… more »
    Top Answer:When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    1st
    out of 41 in Build Automation
    Views
    9,551
    Comparisons
    7,786
    Reviews
    50
    Average Words per Review
    406
    Rating
    8.6
    2nd
    out of 41 in Build Automation
    Views
    6,756
    Comparisons
    5,825
    Reviews
    37
    Average Words per Review
    382
    Rating
    7.9
    Comparisons
    Microsoft Azure DevOps logo
    Compared 50% of the time.
    Bamboo logo
    Compared 5% of the time.
    SonarQube logo
    Compared 5% of the time.
    AWS CodePipeline logo
    Compared 5% of the time.
    GitHub CoPilot logo
    Compared 3% of the time.
    Bamboo logo
    Compared 15% of the time.
    AWS CodePipeline logo
    Compared 10% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Tekton logo
    Compared 6% of the time.
    Harness logo
    Compared 6% of the time.
    Also Known As
    Fuzzit
    Learn More
    Overview

    GitLab is a complete DevOps platform that enables teams to collaborate and deliver software faster. 

    It provides a single application for the entire DevOps lifecycle, from planning and development to testing, deployment, and monitoring. 

    With GitLab, teams can streamline their workflows, automate processes, and improve productivity.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    Sample Customers
    1. NASA  2. IBM  3. Sony  4. Alibaba  5. CERN  6. Siemens  7. Volkswagen  8. ING  9. Ticketmaster  10. SpaceX  11. Adobe  12. Intuit  13. Autodesk  14. Rakuten  15. Unity Technologies  16. Pandora  17. Electronic Arts  18. Nordstrom  19. Verizon  20. Comcast  21. Philips  22. Deutsche Telekom  23. Orange  24. Fujitsu  25. Ericsson  26. Nokia  27. General Electric  28. Cisco  29. Accenture  30. Deloitte  31. PwC  32. KPMG
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    REVIEWERS
    Financial Services Firm16%
    Computer Software Company16%
    Manufacturing Company13%
    Retailer10%
    VISITORS READING REVIEWS
    Educational Organization25%
    Computer Software Company12%
    Financial Services Firm11%
    Manufacturing Company8%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    REVIEWERS
    Small Business44%
    Midsize Enterprise9%
    Large Enterprise47%
    VISITORS READING REVIEWS
    Small Business15%
    Midsize Enterprise34%
    Large Enterprise51%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    GitLab vs. Jenkins
    May 2024
    Find out what your peers are saying about GitLab vs. Jenkins and other solutions. Updated: May 2024.
    771,212 professionals have used our research since 2012.

    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, SonarQube, AWS CodePipeline 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.