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.
"The merging feature makes it easy later on for the deployment."
"I have had no problem with the stability of the solution."
"The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline."
"GitLab's best feature is Actions."
"The most valuable feature of GitLab is its security."
"GitLab is very well-organized and easy to use. Also, it offers most features that customers need."
"I like GitLab's security and SAS tools."
"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."
"Good integration with IDE and JetBrains products."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
"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."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"VCS Trigger: Provides excellent source control support."
"TeamCity is a very user-friendly tool."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"We'd always like to see better pricing on the product."
"I'm new to GitLab, so I would appreciate more documentation about the code and commands."
"The user interface could be more user-friendly. We do most of our operations through the website interface but it could be better."
"We would like to have easier tutorials. Their tutorials are too technical for a user to understand. They should be more detailed but less technical."
"I don't really like the new Kubernetes integration because it is pretty focused on the on-premise environment, but we're in a hybrid environment."
"I rate the support from GitLab a four out of five."
"It is a little complex to set up the pipelines within the solution."
"The solution should be more cloud-native and have more cloud-native capabilities and features."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone) to provide training classes to help newcomers get things up and running more quickly."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"REST API support lacks many features in customization of builds, jobs, and settings."
"I need some more graphical design."
"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."
GitLab is ranked 1st in Build Automation with 70 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. GitLab is rated 8.6, while TeamCity is rated 8.2. 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 GitHub Actions. 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.