Try our new research platform with insights from 80,000+ expert users

AWS CodePipeline vs TeamCity comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

AWS CodePipeline
Ranking in Build Automation
4th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
21
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
10th
Average Rating
8.2
Number of Reviews
28
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the Build Automation category, the mindshare of AWS CodePipeline is 7.1%, down from 9.7% compared to the previous year. The mindshare of TeamCity is 6.8%, down from 7.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Udhay Prakash Pethakamsetty - PeerSpot reviewer
A fully managed service with excellent integrations and a flexible architecture
Compared to any other tools, AWS products provide better integrations. We have tools for all our needs. The integrations are good. The product is a fully managed service. We specify the various stages in the CI/CD process. We can do it without any external tools. Going through everything is usually an overhead for developers. It is like a configuration. We need to configure it only once. The integration with other AWS services has helped us. Our life as a developer is easy. We need not focus on the integration manually. If we work with third-party tools, we must consider connectivity, role management, security, authentication, and authorization. In AWS CodePipeline, if we have IAM roles configured and KMS for the credentials, we need not worry about anything else. Everything can be done within the tool. The integrations are the best part. We can track everything. The connectivity and scalability are good. The architecture is also flexible enough. We can add multiple things.
Omakoji Idakwoji - PeerSpot reviewer
Build management system used to successfully create full request tests and run security scans
I find the TeamCity backend easily accessible. Users can login to the Linux servers that TeamCity is installed on and perform operations. Also I find the ability to template solutions using the meta runner a good feature as well as the user management feature. There is a display that shows which user made recent changes to a branch on GitHub, including the time the changes were made and the particular agent that ran the job. This is also a very useful feature. The metrics and audit available for projects, pipelines and jobs come in handy when debugging.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The integration with other applications is fabulous."
"Another big advantage is observability."
"Code deployment is the best feature."
"The best thing about AWS CodePipeline is that we don't have to manage agents."
"I prefer using CodePipeline and CodeBuild in AWS due to their integration with AWS services, like directly deploying to ECS using Cloud Deploy."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"VCS Trigger: Provides excellent source control support."
"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."
"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."
"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 a very user-friendly tool."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
 

Cons

"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."
"If you're talking about multi-cloud, you can't use it."
"The setup time is a bit long."
"The support team’s response time must be improved."
"AWS CodePipeline functions well, but there's room for improvement in providing technical support to regular customers who haven't purchased developer support. I mean, having it available for everyone, even if it's not a 24-hour service. It would be more useful if specific support hours were available for assistance."
"Improved enhancements and features could make it more intuitive."
"It would be best if AWS CodePipeline provided multiple integration options directly by providing some URLs."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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."
"I would like to see an improvement where TeamCity alerts us via email or another medium if there are discrepancies between the code in the staging environment and what has been deployed to production, such as missing updates."
"If there was more documentation that was easier to locate, it would be helpful for users."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
 

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."
"It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."
"The pricing is manageable."
"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."
"AWS charges you based on the number of pipelines you have and how active they are, and I also think that the root account user knows about all the price-related metrics."
"I would rate the product's pricing a five out of ten."
"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."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
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…
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
15%
Manufacturing Company
7%
Government
7%
Financial Services Firm
28%
Computer Software Company
17%
Manufacturing Company
8%
Government
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Which AWS solution would you choose - CodeStar or CodePipeline?
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 se...
What is your experience regarding pricing and costs for AWS CodePipeline?
I would rate the pricing for CodePipeline at a five out of ten. It depends on other services being used in conjunction with it. The pricing is a bundle.
What do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
What is your experience regarding pricing and costs for TeamCity?
Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.
What needs improvement with TeamCity?
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related ...
 

Comparisons

 

Also Known As

CodePipeline
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about AWS CodePipeline vs. TeamCity and other solutions. Updated: October 2024.
816,406 professionals have used our research since 2012.