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 solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people."
"This product is always evolving, and they listen to the customers."
"The most valuable features of GitLab are the CI/CD pipeline and code management."
"The most important features of GitLab for us are issue management and all the CI/CD tools. Another aspect that I love about GitLab is the UI."
"It is very flexible and easy because you can store data on cloud."
"The solution makes the CI/CD pipelines easy to execute."
"GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos."
"A user friendly solution."
"VCS Trigger: Provides excellent source control support."
"TeamCity's GUI is nice."
"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."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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."
"As GitLab is not perfect, what needs improvement in the solution is the Wiki feature of the groups or the repertories because currently, it's not searchable by default. You'll need an indexing service such as Elasticsearch to make it searchable, and that requires too much work, so for me, it's the main feature that should be improved in GitLab. In the next version of the solution, from the top of my head, the documentation could be improved. Besides the Wiki, it would be good if there's documentation that would be automatically generated based on the code repository. In other words, there should be some tutorials from GitLab for developers in the next release."
"GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful."
"For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."
"There is room for improvement in GitLab Agents."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"It can be free for commercial use."
"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
"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."
"I need some more graphical design."
"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."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
GitLab is ranked 1st in Build Automation with 49 reviews while TeamCity is ranked 6th in Build Automation with 2 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 "User-friendly and easy to configure, but needs better UI". 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.