We performed a comparison between CircleCI 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 automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"It's a stable product."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc."
"The solution offers continuous integration and continuous delivery."
"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."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"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."
"VCS Trigger: Provides excellent source control support."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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."
"Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing."
"Billing is a mess."
"There needs to be some improvement in the user interface of CircleCI."
"The solution’s pricing could be better."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
CircleCI is ranked 11th in Build Automation with 5 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. CircleCI is rated 6.6, while TeamCity is rated 8.2. The top reviewer of CircleCI writes "Unhelpful support, unclear billing, and has offers ability to track usage". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". CircleCI is most compared with Tekton, GitHub Actions, Jenkins, AWS CodeBuild and GoCD, whereas TeamCity is most compared with GitLab, Jenkins, GitHub Actions, Harness and Tekton. See our CircleCI 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.