Try our new research platform with insights from 80,000+ expert users

GitLab vs Jenkins vs TeamCity comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Mindshare comparison

As of October 2025, in the Build Automation category, the mindshare of GitLab is 12.2%, down from 17.0% compared to the previous year. The mindshare of Jenkins is 9.1%, down from 11.4% compared to the previous year. The mindshare of TeamCity is 6.8%, up from 6.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
GitLab12.2%
Jenkins9.1%
TeamCity6.8%
Other71.9%
Build Automation
 

Featured Reviews

Rohit Kesharwani - PeerSpot reviewer
Improved agility and time to market with CI/CD enhancements
The CI/CD pipelines in GitLab are highly valuable. Another important feature is the single source of repository, allowing efficient repository management and source code management. GitLab provides manageability by allowing us to manage source code effectively through separate repositories. Additionally, GitLab enables the creation of individual CI/CD pipelines for each repository, making software more agile. By integrating GitLab as a DevOps platform, we have enhanced agility, improved our time to market, and different teams can work collaboratively on various projects.
Annamalai Pts - PeerSpot reviewer
Streamlined CI/CD pipelines with powerful integration and an easy setup
I use Jenkins as a CI/CD tool. We create pipelines using Jenkins, with stages for Maven builds, Docker image builds, SonarQube integration, and deploying the image to a Kubernetes cluster, AWS EKS Jenkins has made the developers' work very easy. They commit to the remote repository, and…
Almoeeni Fazal - PeerSpot reviewer
Impressive pipeline efficiency with helpful support and a fairly straightforward setup
We use TeamCity for the CI/CD pipeline. It is used for deploying code from the desktop to the production environment. We push our code to GitHub, which then creates a pipeline to a server using AWS, deploying automatically without errors or conflicts in GitHub branches.  We also use TeamCity's…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature of GitLab is the automatic merging of code."
"This is a scalable solution. We had around 200 users working with it."
"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."
"The CI/CD pipeline with Helm has significantly improved deployment speed and efficiency."
"GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos."
"The merging feature makes it easy later on for the deployment."
"The most valuable features of GitLab are the CI/CD pipeline and code management."
"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."
"The most valuable feature of the solution is its integration between different tools."
"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."
"Distributed execution of build and test jobs."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"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."
"Jenkins's open-based framework is very valuable."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
"Good integration with IDE and JetBrains products."
"VCS Trigger: Provides excellent source control support."
"TeamCity's GUI is nice."
 

Cons

"I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities."
"We'd like to see better integration with the Atlassian ecosystem."
"The licensing model could be improved to be more accommodating in terms of user numbers and costs."
"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."
"I would like to see better integration with project management tools such as Jira."
"I'm new to GitLab, so I would appreciate more documentation about the code and commands."
"It is a little complex to set up the pipelines within the solution."
"I rate the support from GitLab a four out of five."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"Some kind of SaaS product would be helpful in providing organizational structure."
"I would like to see even more integrations included in the next release."
"The documentation is not helpful, as it is not user-friendly."
"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."
"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."
"The scriptwriting process could be improved in this solution in the future."
"I need some more graphical design."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."
"If there was more documentation that was easier to locate, it would be helpful for users."
"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
 

Pricing and Cost Advice

"We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."
"The initial setup cost is excellent and you can add the premium features later."
"I think that we pay approximately $100 USD per month."
"The solution is based on a subscription model and is reasonably priced."
"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."
"Regarding pricing, I would rate GitLab as moderately priced, maybe around a seven or eight out of ten. It could be more flexible for clients but generally offers good value."
"This is an open-source solution."
"It seems reasonable. Our IT team manages the licenses."
"We are using the free version of Jenkins. There are no costs or licensing."
"The tool is open-source."
"There is no cost. It is open source."
"Jenkins is open-source, so it is free."
"Jenkins is a free open-source server."
"It's free software with a big community behind it, which is very good."
"Jenkins is open source."
"In our company, we do pay for the licensing of the solution."
"The licensing is on an annual basis."
"Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
869,202 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
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…
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
13%
Government
11%
Manufacturing Company
10%
Financial Services Firm
20%
Computer Software Company
13%
Manufacturing Company
13%
Government
7%
Financial Services Firm
20%
Computer Software Company
18%
Comms Service Provider
8%
Government
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business35
Midsize Enterprise9
Large Enterprise42
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise15
Large Enterprise56
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise15
 

Questions from the Community

What do you like most about GitLab?
I find the features and version control history to be most valuable for our development workflow. These aspects provi...
What is your experience regarding pricing and costs for GitLab?
We are currently using general GitLab, not GitLab Premium.
What needs improvement with GitLab?
GitLab needs to improve the CI/CD functionality because it is not compatible with Jenkins and other tools, as it is n...
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requi...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
What is your experience regarding pricing and costs for Jenkins?
Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of pro...
What do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to diff...
What is your experience regarding pricing and costs for TeamCity?
Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.
What needs improvement with TeamCity?
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it...
 

Comparisons

 

Also Known As

Fuzzit
No data available
No data available
 

Overview

 

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
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: September 2025.
869,202 professionals have used our research since 2012.