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.
"CI/CD is valuable for me."
"The most valuable features of GitLab are the CI/CD pipeline and code management."
"The merging feature makes it easy later on for the deployment."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"The most valuable functionality of GitLab, for me, is the DevOps. Besides the normal source control based on Git, I find the Auto DevOps features most important in the solution."
"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."
"We're only using the basic features of GitLab and haven't used any advanced features. The solution works fine, so that's what we like about GitLab. We're party using GitHub and GitLab. We have a GitHub server, while we use GitLab locally or only within our team, and it works okay. We don't have any significant problems with the solution. We also found the straightforward setup, stability, and scalability of GitLab valuable."
"This product is always evolving, and they listen to the customers."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"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."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity's GUI is nice."
"I would like to see better integration with project management tools such as Jira."
"GitLab can improve by integrating with more tools, such as servers with Docker."
"The documentation is confusing."
"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."
"Expand features to match other tools such as a static code analysis tool so third-party integrations are not required."
"The integration could be slightly better."
"I would like to have some features to support peer review."
"When deploying the solution on cloud and the CI/CD pipeline, we have to define the steps and it becomes confusing."
"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."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"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."
"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."
"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, SonarQube, AWS CodePipeline and Jenkins, whereas TeamCity is most compared with CircleCI, Jenkins, Harness, GitHub Actions and Tekton. 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.