AWS CodeBuild vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
776 views|721 comparisons
JetBrains Logo
3,476 views|3,016 comparisons
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: March 2024).
765,386 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 integration is a good feature.""The integration is a good feature.""The solution provides good integrations."

More AWS CodeBuild Pros →

"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes.""TeamCity is a very user-friendly tool.""The integration is a valuable feature.""It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack.""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.""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.""TeamCity is very useful due to the fact that it has a strong plug-in system."

More TeamCity Pros →

Cons
"They can further improve the integration of the Bitbucket for CodeBuild.""There is no persistent storage or preservation of workspace between the builds."

More AWS CodeBuild Cons →

"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted.""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.""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.""I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""REST API support lacks many features in customization of builds, jobs, and settings.""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.""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."

More TeamCity Cons →

Pricing and Cost Advice
  • "We pay a monthly licensing fee."
  • 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.
    765,386 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 solution provides good integrations.
    Top Answer:The pricing is okay. Jenkins is not costly, but we must pay for the underlying infrastructure. The infrastructure is continuously there for the entire duration. In AWS CodeBuild, we don't have a… more »
    Top Answer:The product must provide more integrations. It is a replica of Jenkins. We have a management overhead. When I build artifacts stored outside the S3 bucket, it will have additional charges on the… more »
    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
    12th
    out of 41 in Build Automation
    Views
    776
    Comparisons
    721
    Reviews
    1
    Average Words per Review
    628
    Rating
    8.0
    6th
    out of 41 in Build Automation
    Views
    3,476
    Comparisons
    3,016
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    Jenkins logo
    Compared 35% of the time.
    GitLab logo
    Compared 25% of the time.
    CircleCI logo
    Compared 17% of the time.
    GitHub Actions logo
    Compared 10% of the time.
    Tekton logo
    Compared 8% 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 Company24%
    Financial Services Firm10%
    Insurance Company6%
    Comms Service Provider6%
    REVIEWERS
    Financial Services Firm14%
    Computer Software Company14%
    Leisure / Travel Company7%
    Non Tech Company7%
    VISITORS READING REVIEWS
    Financial Services Firm22%
    Computer Software Company14%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    VISITORS READING REVIEWS
    Small Business22%
    Midsize Enterprise17%
    Large Enterprise61%
    REVIEWERS
    Small Business38%
    Midsize Enterprise15%
    Large Enterprise46%
    VISITORS READING REVIEWS
    Small Business24%
    Midsize Enterprise10%
    Large Enterprise66%
    Buyer's Guide
    Build Automation
    March 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: March 2024.
    765,386 professionals have used our research since 2012.

    AWS CodeBuild is ranked 12th in Build Automation with 2 reviews while TeamCity is ranked 6th in Build Automation with 24 reviews. AWS CodeBuild is rated 9.0, while TeamCity is rated 8.4. 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.