We performed a comparison between CircleCI and TeamCity based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Amazon and others in Build Automation."The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"The integration is a valuable feature."
"TeamCity is a very user-friendly tool."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"TeamCity's GUI is nice."
"There needs to be some improvement in the user interface of CircleCI."
"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."
"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."
"I need some more graphical design."
CircleCI is ranked 11th in Build Automation with 1 review while TeamCity is ranked 4th in Build Automation with 4 reviews. CircleCI is rated 8.0, while TeamCity is rated 8.0. The top reviewer of CircleCI writes "Beneficial automation workflow and valuable application standardization". On the other hand, the top reviewer of TeamCity writes "User-friendly and easy to configure, but needs better UI". CircleCI is most compared with Tekton, AWS CodePipeline, GoCD, GitLab and Jenkins, whereas TeamCity is most compared with GitLab, Jenkins, Harness, Tekton and Bamboo.
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.
