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'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."
"The merging feature makes it easy later on for the deployment."
"For us, Gitlab's most valuable feature is the integration with Cypress. We're using Cypress as an automation tool, so we're using GitLab as a tool for running in parallel."
"The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good."
"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."
"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."
"It speeds up our development, it's faster, safer, and more convenient."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity is a very user-friendly tool."
"Good integration with IDE and JetBrains products."
"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."
"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."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"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."
"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."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"There is room for improvement in GitLab Agents."
"The user interface could be more user-friendly. We do most of our operations through the website interface but it could be better."
"The price of GitLab could improve, it is high."
"GitLab would be improved with the addition of templates for deployment on local PCs."
"I'm new to GitLab, so I would appreciate more documentation about the code and commands."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I need some more graphical design."
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.
