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."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."
"Permission separations mean that we can grant limited permissions for each team or team member."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"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."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"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."
"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."
"TeamCity's GUI is nice."
"The tool must be more user-friendly."
"The documentation really should be improved by including real examples and more setup cases."
"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."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"I need some more graphical design."
GoCD is ranked 8th 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, Tekton, Microsoft Azure DevOps, GitHub Actions and CircleCI, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and Tekton. 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.
