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 initial setup of GitLab is pretty simple, with no complications."
"The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good."
"Key features allow creation of well-presented Wiki that includes ideas, development, and domains."
"I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools."
"The most valuable feature of GitLab is its convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code."
"The most valuable feature of GitLab is the ability to upload scripts and make changes when needed and then reupload them. Additionally, the solution is user-friendly."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"The SaaS setup is impressive, and it has DAST solutioning."
"TeamCity is a very user-friendly tool."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"VCS Trigger: Provides excellent source control support."
"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."
"The integration is a valuable feature."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"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."
"The only thing our company is really waiting on in terms of features is the development of metrics."
"Some of the scripts that we encountered in GitLab were not fully functional and threw up errors."
"It would be really good if they integrated more features in application security."
"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."
"The solution could be faster."
"There is room for improvement in GitLab Agents."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"GitLab can improve by integrating with more tools, such as servers with Docker."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"REST API support lacks many features in customization of builds, jobs, and settings."
"I need some more graphical design."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
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.