AWS CodePipeline vs TeamCity

Need advice about which tool to choose?Ask the StackShare community!

AWS CodePipeline

384
643
+ 1
30
TeamCity

981
856
+ 1
306
Add tool

AWS CodePipeline vs TeamCity: What are the differences?

What is AWS CodePipeline? Continuous delivery service for fast and reliable application updates. CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.

What is TeamCity? TeamCity is an ultimate Continuous Integration tool for professionals. TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

AWS CodePipeline and TeamCity are primarily classified as "Continuous Deployment" and "Continuous Integration" tools respectively.

Some of the features offered by AWS CodePipeline are:

  • Workflow Modeling
  • AWS Integrations
  • Pre-Built Plugins

On the other hand, TeamCity provides the following key features:

  • Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
  • Simplified setup: create projects from just a VCS repository URL
  • Run multiple builds and tests under different configurations and platforms simultaneously

"Simple to set up" is the top reason why over 3 developers like AWS CodePipeline, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.

According to the StackShare community, TeamCity has a broader approval, being mentioned in 168 company stacks & 51 developers stacks; compared to AWS CodePipeline, which is listed in 30 company stacks and 15 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AWS CodePipeline
Pros of TeamCity
  • 13
    Simple to set up
  • 8
    Managed service
  • 4
    GitHub integration
  • 3
    Parallel Execution
  • 2
    Automatic deployment
  • 0
    Manual Steps Available
  • 59
    Easy to configure
  • 37
    Reliable and high-quality
  • 31
    User friendly
  • 31
    Github integration
  • 31
    On premise
  • 18
    Great UI
  • 16
    Smart
  • 12
    Free for open source
  • 12
    Can run jobs in parallel
  • 8
    Crossplatform
  • 4
    Chain dependencies
  • 4
    Great support by jetbrains
  • 4
    Fully-functional out of the box
  • 4
    Projects hierarchy
  • 4
    REST API
  • 3
    100+ plugins
  • 3
    Free for small teams
  • 3
    Per-project permissions
  • 3
    Personal notifications
  • 3
    Build templates
  • 2
    Ide plugins
  • 2
    GitLab integration
  • 2
    Smart build failure analysis and tracking
  • 2
    Upload build artifacts
  • 2
    Artifact dependencies
  • 2
    Build progress messages promoting from running process
  • 1
    TeamCity Professional is FREE
  • 1
    Powerful build chains / pipelines
  • 1
    Built-in artifacts repository
  • 1
    Repository-stored, full settings dsl with ide support
  • 0
    Official reliable support
  • 0
    High-Availability
  • 0
    Hosted internally

Sign up to add or upvote prosMake informed product decisions

Cons of AWS CodePipeline
Cons of TeamCity
  • 2
    No project boards
  • 1
    No integration with "Power" 365 tools
  • 1
    Proprietary
  • 1
    High costs for more than three build agents
  • 1
    User friendly
  • 1
    User-friendly

Sign up to add or upvote consMake informed product decisions

What is AWS CodePipeline?

CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.

What is TeamCity?

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Need advice about which tool to choose?Ask the StackShare community!

What companies use AWS CodePipeline?
What companies use TeamCity?
See which teams inside your own company are using AWS CodePipeline or TeamCity.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with AWS CodePipeline?
What tools integrate with TeamCity?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to AWS CodePipeline and TeamCity?
AWS CodeDeploy
AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications.
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
AWS CodeBuild
AWS CodeBuild is a fully managed build 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.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
AWS CodeStar
Start new software projects on AWS in minutes using templates for web applications, web services and more.
See all alternatives
How developers use AWS CodePipeline and TeamCity
DigitalPermits uses
TeamCity

TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned.

Stack Exchange uses
TeamCity

TeamCity builds then copies to each web tier via a powershell script. The steps for each server are:

  • Tell HAProxy to take the server out of rotation via a POST
  • Delay to let IIS finish current requests (~5 sec)
  • Stop the website (via the same PSSession for all the following)
  • Robocopy files
  • Start the website
  • Re-enable in HAProxy via another POST
Sascha Manns uses
TeamCity

I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.

Andrew King uses
TeamCity

Continuous integration for iOS apps.

One Legal uses
TeamCity

Build system.