We performed a comparison between AWS CodeBuild 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 solution provides good integrations."
"The integration with other AWS services has streamlined our workflow."
"The integration is a good feature."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration is a good feature."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"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."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"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."
"TeamCity is a very user-friendly tool."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"VCS Trigger: Provides excellent source control support."
"There is no persistent storage or preservation of workspace between the builds."
"They can further improve the integration of the Bitbucket for CodeBuild."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"The deployment fails sometimes."
"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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"I need some more graphical design."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
AWS CodeBuild is ranked 9th in Build Automation with 4 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. AWS CodeBuild is rated 8.8, while TeamCity is rated 8.2. The top reviewer of AWS CodeBuild writes "Provides good integrations, is flexible, and has a comparable price". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". AWS CodeBuild is most compared with Jenkins, GitLab, GitHub Actions, CircleCI and Tekton, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, GitHub Actions and Harness. See our AWS CodeBuild 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.
