TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    AWS CodePipeline

    Score6.6 out of 10
    N/AAWS CodePipeline is a fully managed continuous delivery service that helps users automate release pipelines. CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the release model a user defines.

    $1

    per active pipeline/per month

    TeamCity

    Score7.1 out of 10
    N/ATeamCity is a continuous integration server from Czeck company JetBrains.N/A

    Travis CI

    Score7.3 out of 10
    N/ATravis CI is an open source continuous integration platform, that enables users to run and test simultaneously on different environments, and automatically catch code failures and bugs.

    $69

    per month 1 concurrent job

    Pricing
    AWS CodePipelineTeamCityTravis CI
    Editions & Modules
    AWS CodePipeline
    $1
    per active pipeline/per month
    Free Tier
    Free
    No answers on this topic
    1 Concurrent Job Plan
    $69
    per month
    Bootstrap
    $69
    per month 1 concurrent job
    2 Concurrent Jobs Plan
    $129
    per month
    Startup
    $129
    per month 2 concurrent jobs
    5 Concurrent Jobs Plan
    $249
    per month
    Small Business
    $249
    per month 5 concurrent jobs
    Premium
    $489
    per month 10 concurrent jobs
    Platinum
    $794+
    per month starting at 15 concurrent jobs
    Free Plan
    Free
    Offerings
    Pricing Offerings
    AWS CodePipelineTeamCityTravis CI
    Free Trial
    NoNoYes
    Free/Freemium Version
    YesNoYes
    Premium Consulting/Integration Services
    NoNoNo
    Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
    Additional Details——Discount available for annual pricing.
    More Pricing Information
    Community Pulse
    AWS CodePipelineTeamCityTravis CI
    Considered Multiple Products
    Amazon AWS
    Chose AWS CodePipeline
    We selected AWS CodePipeline mainly because we wanted to keep the application stack completely native to AWS, and CodePipeline provided the best integrations with AWS services that we were using, such as S3, Elastic Beanstalk, and Lamba. Furthermore, AWS CodePipeline provided …
    Incentivized
    Chose AWS CodePipeline
    AWS Codepipeline is proprietary to Amazon Web Services and works well when you're working with other AWS products. If you're using a different technology stack, then Codepipeline may not be the best tool and some open source/closed source tools available on the web may suffice.
    Incentivized
    Chose AWS CodePipeline
    I felt that, out of the alternatives, AWS CodePipeline was the simplest to setup and most reliable. Since my client's infrastructure was already hosted in AWS, I felt it was a no-brainer. If a client needed a similar solution with on-prem or non-AWS infrastructure, I would …
    Incentivized
    JetBrains
    Chose TeamCity
    I would also like to compare TeamCity against Snap-Ci as well as Concourse. We chose TeamCity over all of these tools because of its ability to be set up easily against a restricting corporate firewall. We needed to integrate unit tests, integration tests, pushes to production, …
    Incentivized
    Idera, Inc.
    Chose Travis CI
    Jenkins is much more complicated to configure and start using. Although, one you have done that, it's extremely powerful and full of features. Maybe many more than Travis CI. As per TeamCity, I would never go back to using it. It's also complicated to configure but it is not …
    Incentivized
    Key User Insights
    Would buy again
    No answers on this topic
    100%
    Would buy again
    5 Answers
    No answers on this topic
    Delivers good value for the price
    No answers on this topic
    No answers on this topic
    No answers on this topic
    Happy with the feature set
    No answers on this topic
    100%
    Happy with the feature set
    5 Answers
    No answers on this topic
    Lived up to sales and marketing promises
    No answers on this topic
    No answers on this topic
    No answers on this topic
    Implementation went as expected
    No answers on this topic
    No answers on this topic
    No answers on this topic
    Best Alternatives
    AWS CodePipelineTeamCityTravis CI
    Small Businesses
    CircleCI
    Score9.3 out of 10
    Apache Maven
    Score9 out of 10
    Apache Maven
    Score9 out of 10
    Medium-sized Companies
    CircleCI
    Score9.3 out of 10
    Apache Maven
    Score9 out of 10
    Apache Maven
    Score9 out of 10
    Enterprises
    CircleCI
    Score9.3 out of 10
    Gradle Build Tool (Open Source)
    Score9 out of 10
    Gradle Build Tool (Open Source)
    Score9 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    AWS CodePipelineTeamCityTravis CI
    Likelihood to Recommend
    9.0
    (8 ratings)
    10.0
    (18 ratings)
    6.0
    (8 ratings)
    Usability
    9.0
    (1 ratings)
    -
    (0 ratings)
    5.0
    (1 ratings)
    Performance
    6.8
    (2 ratings)
    9.3
    (2 ratings)
    -
    (0 ratings)
    Support Rating
    9.1
    (2 ratings)
    -
    (0 ratings)
    4.0
    (1 ratings)
    Ease of integration
    7.4
    (2 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    User Testimonials
    AWS CodePipelineTeamCityTravis CI
    Likelihood to Recommend
    Amazon AWS
    I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.
    Incentivized
    Read full review
    JetBrains
    TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.
    Incentivized
    Read full review
    Idera, Inc.
    TravisCI is suited for workflows involving typical software development but unfortunately I think the software needs more improvement to be up to date with current development systems and TravisCI hasn't been improving much in that space in terms of integrations.
    Incentivized
    Read full review
    Pros
    Amazon AWS
    • It is reliable and works without errors
    • It integrates well with our repository and all other AWS functions as well as our end database
    Incentivized
    Read full review
    JetBrains
    • TeamCity provides a great integration with git, especially Bitbucket.
    • When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
    • TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.
    Incentivized
    Read full review
    Idera, Inc.
    • It is very simple to configure a range of environment versions and settings in a simple YAML file.
    • It integrates very well with Github, Bitbucket, or a private Git repo.
    • The Travis CI portal beautifully shows you your history and console logs. Everything is presented in a very clear and intuitive interface.
    Incentivized
    Read full review
    Cons
    Amazon AWS
    • Ease of use - things like CircleCI or other tools are a bit easier to learn.
    • Ability to build from more sources.
    Incentivized
    Read full review
    JetBrains
    • The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
    • Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
    Incentivized
    Read full review
    Idera, Inc.
    • I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
    • There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.
    Incentivized
    Read full review
    Usability
    Amazon AWS
    Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.
    Incentivized
    Read full review
    JetBrains
    No answers on this topic
    Idera, Inc.
    TravisCI hasn't had much changes made to its software and has thus fallen behind compared to many other CI/CD applications out there. I can only give it a 5 because it does what it is supposed to do but lacks product innovation.
    Incentivized
    Read full review
    Performance
    Amazon AWS
    Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.
    Incentivized
    Read full review
    JetBrains
    TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
    Incentivized
    Read full review
    Idera, Inc.
    No answers on this topic
    Support Rating
    Amazon AWS
    We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.
    Incentivized
    Read full review
    JetBrains
    No answers on this topic
    Idera, Inc.
    After the private equity firm had bought this company the innovation and support has really gone downhill a lot. I am not a fan that they have gutted the software trying to make money from it and put innovation and product development second.
    Incentivized
    Read full review
    Alternatives Considered
    Amazon AWS
    CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for Beanstalk, which is often used as a deployment target in relation to CodePipeline.

    CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via Beanstalk.

    Jenkins is open source and not a native AWS service, that is its primary differentiator. Jenkins can also be used as a supplement to CodePipeline.
    Incentivized
    Read full review
    JetBrains
    TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
    Incentivized
    Read full review
    Idera, Inc.
    Jenkins is much more complicated to configure and start using. Although, one you have done that, it's extremely powerful and full of features. Maybe many more than Travis CI. As per TeamCity, I would never go back to using it. It's also complicated to configure but it is not worth the trouble. Codeship supports integration with GitHub, GitLab and BitBucket. I've only used it briefly, but it seems to be a nice tool.
    Incentivized
    Read full review
    Return on Investment
    Amazon AWS
    • CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
    • CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
    • CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.
    Incentivized
    Read full review
    JetBrains
    • TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
    • TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
    • TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.
    Incentivized
    Read full review
    Idera, Inc.
    • It's improved my ability to deliver working code, increasing my development velocity.
    • It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage.
    • It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build).
    • It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high).
    • The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch".
    Incentivized
    Read full review
    ScreenShots