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.
"It scales well."
"As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab."
"We have seen a couple of merge requests or pull requests raised in GitLab. I see the interface, the way it shows the difference between the two source codes, that it is easy for anyone to do the review and then accept the request; the pull request is the valuable feature."
"The stability is good."
"GitLab is a solution for source code management, container registry, pipelines, testing, and deployment."
"GitLab offers a good interface for doing code reviews between two colleagues."
"We use the Git repository and tagging feature. We are a product-based company and use this solution to move to a forward or backward tag."
"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
"TeamCity's GUI is nice."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"Good integration with IDE and JetBrains products."
"TeamCity is a very user-friendly tool."
"VCS Trigger: Provides excellent source control support."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"The solution could be faster."
"I would like to have some features to support peer review."
"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."
"I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities."
"The only thing our company is really waiting on in terms of features is the development of metrics."
"Expand features to match other tools such as a static code analysis tool so third-party integrations are not required."
"We do face issues in our company when we run out of disk space."
"GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users."
"If there was more documentation that was easier to locate, it would be helpful for users."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"I need some more graphical design."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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."
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.