AWS CodePipeline vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Amazon Web Services (AWS) Logo
4,844 views|3,796 comparisons
92% 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 CodePipeline 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.
To learn more, read our detailed AWS CodePipeline vs. TeamCity Report (Updated: March 2024).
768,886 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
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps.""The product is cost-effective and integrates well with the AWS environment.""The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier.""The most valuable feature of AWS CodePipeline is the flexibility of the configuration.""It's a perfect solution if you are just using AWS.""The integration with other applications is fabulous.""The integrations are good.""AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."

More AWS CodePipeline Pros →

"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.""It's easy to move to a new release because of templates and meta-runners, and agent pooling.""VCS Trigger: Provides excellent source control support.""The integration is a valuable feature.""We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted.""Good integration with IDE and JetBrains products.""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."

More TeamCity Pros →

Cons
"The setup time is a bit long.""If you're talking about multi-cloud, you can't use it.""The product’s pricing needs improvement.""The tool does not provide automated features for evidence collection.""There could be a possibility of deploying tag-based conditions for different environments using the same code base.""The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation.""AWS CodePipeline doesn't offer much room for customization.""It would be a much better tool if it could be made compatible with other cloud services as well since this is an area the product currently lacks."

More AWS CodePipeline Cons →

"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""The upgrade process could be smoother. Upgrading major versions can often cause some pain.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""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.""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.""REST API support lacks many features in customization of builds, jobs, and settings.""Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."

More TeamCity Cons →

Pricing and Cost Advice
  • "The pricing of this solution is dependent upon your needs including how many jobs you daily and how many times the developer will be changing codes and completing deployments."
  • "I would rate the product's pricing a five out of ten."
  • "AWS offers free business or enterprise support services."
  • "It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."
  • "The product is quite expensive compared to other solutions."
  • "AWS CodePipeline is quite affordable. I've been running around four pipelines and the cost is around one dollar per month. It rarely exceeds two dollars."
  • "Compared to other cloud services, AWS CodePipeline falls a bit more on the pricey side. I see that the price of the product has been increasing for the past few years."
  • More AWS CodePipeline 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,886 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:Both AWS solutions deliver solid options, with uniquely different features. AWS CodeStar allows for quick development, building, and deployments of apps. It also provides web application and web… more »
    Top Answer:The product is quite expensive compared to other solutions.
    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
    4th
    out of 41 in Build Automation
    Views
    4,844
    Comparisons
    3,796
    Reviews
    9
    Average Words per Review
    384
    Rating
    8.2
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    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.
    Incredibuild logo
    Compared 2% of the time.
    Also Known As
    CodePipeline
    Learn More
    Overview

    AWS CodePipeline is a fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you define. This enables you to rapidly and reliably deliver features and updates. You can easily integrate AWS CodePipeline with third-party services such as GitHub or with your own custom plugin. With AWS CodePipeline, you only pay for what you use. There are no upfront fees or long-term commitments.

    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
    REVIEWERS
    Computer Software Company25%
    Transportation Company13%
    Comms Service Provider13%
    Government13%
    VISITORS READING REVIEWS
    Computer Software Company19%
    Financial Services Firm14%
    Comms Service Provider8%
    Manufacturing Company7%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Non Tech Company7%
    Hospitality Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    REVIEWERS
    Small Business38%
    Midsize Enterprise15%
    Large Enterprise46%
    VISITORS READING REVIEWS
    Small Business24%
    Midsize Enterprise13%
    Large Enterprise63%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    Buyer's Guide
    AWS CodePipeline vs. TeamCity
    March 2024
    Find out what your peers are saying about AWS CodePipeline vs. TeamCity and other solutions. Updated: March 2024.
    768,886 professionals have used our research since 2012.

    AWS CodePipeline is ranked 4th in Build Automation with 13 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. AWS CodePipeline is rated 8.4, while TeamCity is rated 8.2. The top reviewer of AWS CodePipeline writes "A fully managed service with excellent integrations and a flexible architecture". 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 CodePipeline is most compared with GitLab, AWS CodeStar, Jenkins, GitHub Actions and Harness, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and Incredibuild. See our AWS CodePipeline 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.