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.
"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."
"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."
"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."
"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."
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.