We performed a comparison between GoCD and TeamCity based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Permission separations mean that we can grant limited permissions for each team or team member."
"The UI is colorful."
"The most notable aspect is its user interface, which we find to be user-friendly and straightforward for deploying and comprehending pipelines. We have the ability to create multiple pipelines, and in addition to that, the resource consumption is impressive."
"TeamCity's GUI is nice."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"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."
"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 most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
"VCS Trigger: Provides excellent source control support."
"The integration is a valuable feature."
"The documentation really should be improved by including real examples and more setup cases."
"The tool must be more user-friendly."
"The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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 need some more graphical design."
"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."
"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."
GoCD is ranked 10th in Build Automation with 6 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. GoCD is rated 7.6, while TeamCity is rated 8.2. The top reviewer of GoCD writes "User-friendly, useful multiple pipeline capabilities, and low resource consumption". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". GoCD is most compared with GitLab, Microsoft Azure DevOps, GitHub Actions, Tekton and CircleCI, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, GitHub Actions and Harness. See our GoCD 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.