Cancel
You must select at least 2 products to compare!
GitLab Logo
9,859 views|7,926 comparisons
JetBrains Logo
3,476 views|3,016 comparisons
Comparison Buyer's Guide
Executive Summary
Updated on Mar 6, 2024

We compared TeamCity and GitLab based on our user's reviews in several parameters.

Overall, TeamCity users have expressed the need for improvement in areas such as user interface, documentation, integration capabilities, and performance. On the other hand, GitLab users find the pricing, setup cost, and licensing reasonable and flexible. Enhancement suggestions focus on user interface, performance, and project management features. GitLab's customer service is highly praised, while TeamCity users have highlighted its positive impact on project management and efficiency.

Features: TeamCity stands out for its seamless integration with various build tools, intuitive interface, efficient project management, extensive customization options, and strong support for test management. Meanwhile, GitLab is appreciated for its robust version control, collaborative tools, powerful CI/CD pipelines, comprehensive issue tracking system, customizable workflows, and security measures.

Pricing and ROI: The setup cost of TeamCity and GitLab differs in terms of users' satisfaction. TeamCity's setup cost is manageable without complications, whereas GitLab offers easy and straightforward setup. As for licensing, TeamCity has a straightforward process, while GitLab provides flexible and convenient options., The ROI from TeamCity is praised for its positive impact on project management, increased efficiency, and improved collaboration. GitLab users express satisfaction and highlight the platform's valuable investment for their projects or businesses.

Room for Improvement: TeamCity could improve its user interface and support for integration with other tools, as well as provide more detailed documentation. Users also desire better performance and responsiveness. In comparison, GitLab could enhance its user interface, navigation, performance for larger projects, project management features, and code review process.

Deployment and customer support: User feedback for TeamCity suggests that the duration to establish a new tech solution varies depending on circumstances. Some spend 3 months on deployment and an additional week on setup, while others spend a week on both. GitLab feedback also varies, with some spending 3 months on deployment and a week on setup, and others spending a week on both., Customers have expressed satisfaction with the customer service in TeamCity. Meanwhile, GitLab's customer service is highly praised for its prompt assistance, effective troubleshooting, helpful guidance, and dedication to assisting users. GitLab also offers detailed documentation and a strong community for collaboration.

The summary above is based on 52 interviews we conducted recently with TeamCity and GitLab users. To access the review's full transcripts, download our report.

To learn more, read our detailed GitLab vs. TeamCity Report (Updated: March 2024).
765,234 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
"GitLab is a solution for source code management, container registry, pipelines, testing, and deployment.""GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable.""GitLab integrates well with other platforms.""We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people.""GitLab is very well-organized and easy to use. Also, it offers most features that customers need.""The most valuable features of GitLab are the CI/CD pipeline and code management.""The most valuable features of GitLab are the review, patch repo, and plans are in YAML.""We like that we can have an all-encompassing product and don't have to implement different solutions."

More GitLab Pros →

"VCS Trigger: Provides excellent source control support.""The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications.""It's easy to move to a new release because of templates and meta-runners, and agent pooling.""TeamCity is a very user-friendly tool.""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.""Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end.""Good integration with IDE and JetBrains products.""The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."

More TeamCity Pros →

Cons
"GitLab's Windows version is yet not available and having this would be an improvement.""It can be free for commercial use.""Their RBAC is role-based access, which is fine but not very good.""I rate the support from GitLab a four out of five.""Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict.""We do face issues in our company when we run out of disk space.""I would like to have some features to support peer review.""It should be used by a larger number of people. They should raise awareness."

More GitLab Cons →

"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.""REST API support lacks many features in customization of builds, jobs, and settings.""The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs.""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.""If there was more documentation that was easier to locate, it would be helpful for users.""Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted.""I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""It will benefit this solution if they keep up to date with other CI/CD systems out there."

More TeamCity 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 →

  • "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."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    765,234 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:The solution makes the CI/CD pipelines easy to execute.
    Top Answer:The tool should include a feature that helps to edit the code directly.
    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in… more »
    Ranking
    1st
    out of 41 in Build Automation
    Views
    9,859
    Comparisons
    7,926
    Reviews
    48
    Average Words per Review
    401
    Rating
    8.6
    6th
    out of 41 in Build Automation
    Views
    3,476
    Comparisons
    3,016
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    Microsoft Azure DevOps logo
    Compared 47% of the time.
    Bamboo logo
    Compared 6% of the time.
    AWS CodePipeline logo
    Compared 5% of the time.
    SonarQube logo
    Compared 4% of the time.
    Jenkins logo
    Compared 3% of the time.
    CircleCI logo
    Compared 17% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 7% of the time.
    Tekton logo
    Compared 6% of the time.
    Bamboo logo
    Compared 5% 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.

    TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

    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
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    REVIEWERS
    Financial Services Firm16%
    Computer Software Company16%
    Manufacturing Company13%
    Retailer10%
    VISITORS READING REVIEWS
    Educational Organization25%
    Computer Software Company12%
    Financial Services Firm10%
    Manufacturing Company8%
    REVIEWERS
    Financial Services Firm14%
    Computer Software Company14%
    Non Tech Company7%
    Leisure / Travel Company7%
    VISITORS READING REVIEWS
    Financial Services Firm22%
    Computer Software Company14%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    REVIEWERS
    Small Business44%
    Midsize Enterprise9%
    Large Enterprise47%
    VISITORS READING REVIEWS
    Small Business15%
    Midsize Enterprise34%
    Large Enterprise52%
    REVIEWERS
    Small Business38%
    Midsize Enterprise15%
    Large Enterprise46%
    VISITORS READING REVIEWS
    Small Business24%
    Midsize Enterprise10%
    Large Enterprise66%
    Buyer's Guide
    GitLab vs. TeamCity
    March 2024
    Find out what your peers are saying about GitLab vs. TeamCity and other solutions. Updated: March 2024.
    765,234 professionals have used our research since 2012.

    GitLab is ranked 1st in Build Automation with 68 reviews while TeamCity is ranked 6th in Build Automation with 24 reviews. GitLab is rated 8.6, while TeamCity is rated 8.4. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". GitLab is most compared with Microsoft Azure DevOps, Bamboo, AWS CodePipeline, SonarQube and Jenkins, whereas TeamCity is most compared with CircleCI, Jenkins, Harness, Tekton and Bamboo. See our GitLab vs. TeamCity 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.