IT Central Station is now PeerSpot: Here's why

GitLab vs Jenkins comparison

You must select at least 2 products to compare!
GitLab Logo
15,293 views|13,557 comparisons
Jenkins Logo
10,418 views|9,021 comparisons
Featured Review
Buyer's Guide
GitLab vs. Jenkins
May 2022
Find out what your peers are saying about GitLab vs. Jenkins and other solutions. Updated: May 2022.
607,178 professionals have used our research since 2012.
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
"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.""GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable.""The stability is good.""I like that it's easy to deploy our services over GitLab. The customer support is also good with a really active community. You have a lot of support that you can get online with your stack. That is probably one of the benefits of using GitLab. It's also really fast.""A user friendly solution.""GitLab integrates well with other platforms.""GitLab offers a good interface for doing code reviews between two colleagues.""CI/CD is very good. The version control system is also good. These are the two features that we use."

More GitLab Pros →

"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case.""Very easy to understand for newcomers.""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.""The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly.""The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins.""The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization.""Jenkins is very stable.""With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."

More Jenkins Pros →

"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.""I would like to see better integration with project management tools such as Jira.""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.""The solution should be more cloud-native and have more cloud-native capabilities and features.""In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents.""We'd like to see better integration with the Atlassian ecosystem.""We would like to generate document pages from the sources.""I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version."

More GitLab Cons →

"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.""There is no way for the cloud repositories to trigger Jenkins.""I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it.""It could be cheaper.""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.""A more user-friendly UI for creating pipelines would be helpful.""The UI of Jenkins could improve.""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."

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 →

  • "There is no cost. It is open source."
  • "The solution is one of the lowest costs compared to competitors."
  • "It could be cheaper because there are many solutions available in the market. We are paying yearly."
  • "Jenkins is a free open-source server."
  • "We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."
  • "We are using the freeware version of Jenkins."
  • More Jenkins Pricing and Cost Advice →

    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    607,178 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:Of all available products, it was the easiest to use and easy to install.
    Top Answer:When I was hired (in 2020) they told me that they were using an open-source version. I'm not sure if that's still the case as it's a quite big company. Nowadays they should be using some kind of paid… more »
    Top Answer:The solution should be more cloud-native and have more cloud-native capabilities and features. It should be more GitOps-ready.
    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:The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions.
    out of 34 in Build Automation
    Average Words per Review
    out of 34 in Build Automation
    Average Words per Review
    Tekton logo
    Compared 44% of the time.
    TeamCity logo
    Compared 8% of the time.
    Bamboo logo
    Compared 7% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    GoCD logo
    Compared 4% of the time.
    Learn More

    GitLab is a single application with features for the whole software development and operations (DevOps) lifecycle.

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

    Learn more about GitLab
    Learn more about Jenkins
    Sample Customers
    Siemens, University of Washington, Equinix, Paessler AG, CNCF, Ticketmaster, CERN, Vaadin
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    Computer Software Company27%
    Mining And Metals Company13%
    Manufacturing Company13%
    Computer Software Company22%
    Comms Service Provider20%
    Financial Services Firm8%
    Financial Services Firm38%
    Computer Software Company27%
    Media Company15%
    Computer Software Company21%
    Comms Service Provider16%
    Financial Services Firm13%
    Manufacturing Company11%
    Company Size
    Small Business44%
    Midsize Enterprise8%
    Large Enterprise48%
    Small Business19%
    Midsize Enterprise16%
    Large Enterprise65%
    Small Business29%
    Midsize Enterprise12%
    Large Enterprise59%
    Small Business15%
    Midsize Enterprise14%
    Large Enterprise70%
    Buyer's Guide
    GitLab vs. Jenkins
    May 2022
    Find out what your peers are saying about GitLab vs. Jenkins and other solutions. Updated: May 2022.
    607,178 professionals have used our research since 2012.

    GitLab is ranked 1st in Build Automation with 23 reviews while Jenkins is ranked 2nd in Build Automation with 23 reviews. GitLab is rated 8.2, while Jenkins is rated 8.0. The top reviewer of GitLab writes "A double-sided solution for both DevOps and version management". On the other hand, the top reviewer of Jenkins writes "We can do whatever we want and customize as much as we wish to in any programming language". GitLab is most compared with Microsoft Azure DevOps, TeamCity, Tekton, Sonatype Nexus Lifecycle and Black Duck, whereas Jenkins is most compared with Tekton, TeamCity, Bamboo, IBM Rational Build Forge and GoCD. 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.