AWS CodeBuild vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
781 views|724 comparisons
100% willing to recommend
JetBrains Logo
3,373 views|2,977 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between AWS CodeBuild and TeamCity based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
768,740 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The solution provides good integrations.""The integration is a good feature.""The integration is a good feature.""It works seamlessly with AWS Elastic Container Registry (ECR).""The integration with other AWS services has streamlined our workflow."

More AWS CodeBuild Pros →

"Good integration with IDE and JetBrains products.""TeamCity's GUI is nice.""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.""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.""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 integration is a valuable feature.""VCS Trigger: Provides excellent source control support."

More TeamCity Pros →

Cons
"There is no persistent storage or preservation of workspace between the builds.""While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected.""They can further improve the integration of the Bitbucket for CodeBuild.""The deployment fails sometimes."

More AWS CodeBuild Cons →

"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.""I need some more graphical design.""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.""Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity.""It will benefit this solution if they keep up to date with other CI/CD systems out there."

More TeamCity Cons →

Pricing and Cost Advice
  • "We pay a monthly licensing fee."
  • "Despite the cost, it is worth the investment."
  • More AWS CodeBuild Pricing and Cost Advice →

  • "Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,740 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:The integration is a good feature.
    Top Answer:They can further improve the integration of the Bitbucket for CodeBuild.
    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in… more »
    Ranking
    9th
    out of 41 in Build Automation
    Views
    781
    Comparisons
    724
    Reviews
    2
    Average Words per Review
    386
    Rating
    9.0
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    Jenkins logo
    Compared 36% of the time.
    GitLab logo
    Compared 24% of the time.
    CircleCI logo
    Compared 16% of the time.
    GitHub Actions logo
    Compared 11% of the time.
    Tekton logo
    Compared 7% of the time.
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 17% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 7% of the time.
    Tekton logo
    Compared 6% of the time.
    Also Known As
    CodeBuild
    Learn More
    Overview

    AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers. CodeBuild scales continuously and processes multiple builds concurrently, so your builds are not left waiting in a queue. You can get started quickly by using prepackaged build environments, or you can create custom build environments that use your own build tools. With CodeBuild, you are charged by the minute for the compute resources you use.

    TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

    Sample Customers
    Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company23%
    Financial Services Firm10%
    Insurance Company6%
    Comms Service Provider6%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Leisure / Travel Company7%
    Non Tech Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company9%
    Comms Service Provider7%
    Company Size
    VISITORS READING REVIEWS
    Small Business22%
    Midsize Enterprise17%
    Large Enterprise62%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    768,740 professionals have used our research since 2012.

    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, CircleCI, GitHub Actions and Tekton, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and Tekton.

    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.