No more typing reviews! Try our Samantha, our new voice AI agent.

AWS CodePipeline vs Travis CI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 3, 2026

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
6th
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
20th
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 July 2026, in the Build Automation category, the mindshare of AWS CodePipeline is 3.1%, down from 5.1% compared to the previous year. The mindshare of Travis CI is 3.3%, up from 0.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
AWS CodePipeline3.1%
Travis CI3.3%
Other93.6%
Build Automation
 

Featured Reviews

JR
Head of Development at Abyss
Employs advanced deployment strategies and manages CI/CD workflow efficiently
Blue-green deployment has been incredibly beneficial for handling complex deployments in AWS CodePipeline. It allows me to test changes in an isolated environment before deploying them to the entire user base. Additionally, the CI/CD support provided by AWS simplifies the integration process by adding YAML files to projects, enabling AWS to manage the entire CI/CD workflow.
Pravar Agrawal - PeerSpot reviewer
Senior SRE at a tech vendor with 10,001+ employees
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 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 solution's technical support responds whenever you have an issue, especially whenever you need something sorted out from their side."
"The management of CodeBuild and CodeDeploy on a three-point trigger basis is an important feature."
"Blue-green deployment has been incredibly beneficial for handling complex deployments in AWS CodePipeline as it allows me to test changes in an isolated environment before deploying them to the entire user base."
"AWS CodePipeline has valuable integration features."
"Code deployment is the best feature."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"The solution is pretty stable and it's a perfect solution if you are just using AWS."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"I would appreciate if we don't have to install any agents, even for EC2, to deploy using CodeDeploy into EC2 servers. It would help if AWS allows application deployment without requiring the Fortify agent installation."
"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."
"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."
"The migration process from one source code to another needs improvement."
"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."
"If there are many dependancies involved in the setup, it may take a long time."
"From my perspective, some in-built capabilities could be enhanced."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"The pricing is manageable."
"The price of the product depends on how many times you run it. The tool offers a pay-as-you-go model."
"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."
"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."
"It is a straightforward approach where you pay for the resources you consume as they offer a subscription-based licensing model."
"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 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 product is quite expensive compared to other solutions."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
902,988 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Educational Organization
8%
Comms Service Provider
6%
Computer Software Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise4
Large Enterprise7
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 needs improvement with AWS CodePipeline?
The documentation for AWS CodePipeline is lacking and makes it difficult to find information due to its complexity. It would be helpful to have examples in the documentation for different project t...
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, Jenkins, GitHub and others in Build Automation. Updated: May 2026.
902,988 professionals have used our research since 2012.