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

AWS CodePipeline vs Travis CI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

Review summaries and opinions

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

Categories and Ranking

AWS CodePipeline
Ranking in Build Automation
5th
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
23
Ranking in other categories
No ranking in other categories
Travis CI
Ranking in Build Automation
21st
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2025, in the Build Automation category, the mindshare of AWS CodePipeline is 5.0%, down from 8.0% compared to the previous year. The mindshare of Travis CI is 1.0%, down from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Istiyak Ahmed - PeerSpot reviewer
Streamlined deployment through excellent integration with a straightforward setup
Our primary use case for CodePipeline involves deploying the different services, such as hosting a website on ECS or EC2 and deploying source code on container services or EC2 instances. We configure the source code with remote repositories like GitHub or Bitbucket, build the code, and store images…
Pravar Agrawal - PeerSpot reviewer
YAML-based configuration and simple deployment but user interface needs modernizing
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Quotes from Members

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

Pros

"The management of CodeBuild and CodeDeploy on a three-point trigger basis is an important feature."
"AWS CodePipeline has valuable integration features."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"The best thing about AWS CodePipeline is that we don't have to manage agents."
"The product is cost-effective and integrates well with the AWS environment."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"CodePipeline allows integration with any source code and facilitates deployment to EC2 or ECS, which is highly valuable."
"The notification and approval approach in the production environment are very useful."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"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."
"AWS CodePipeline works effectively, and I haven't identified any specific areas needing improvement as it has been quite satisfying in terms of deployment needs."
"In the next release, I would like to see fewer timeout errors."
"From my perspective, some in-built capabilities could be enhanced."
"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."
"The migration process from one source code to another needs improvement."
"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."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"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."
"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 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."
"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."
"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."
"The price of the product depends on how many times you run it. The tool offers a pay-as-you-go model."
"AWS offers free business or enterprise support services."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
865,140 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Government
8%
Manufacturing Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

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?
AWS CodePipeline's pricing is reasonable, and it is not too expensive. I estimated it costs around $5 monthly. On a scale from one to ten, where one is very cheap and ten is very expensive, I would...
What is your experience regarding pricing and costs for Travis CI?
I'm not too sure about the pricing of Travis or how the agreement works.
What needs improvement with Travis CI?
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user...
What is your primary use case for Travis CI?
Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...
 

Comparisons

 

Also Known As

CodePipeline
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: July 2025.
865,140 professionals have used our research since 2012.