AWS CodeBuild vs Travis CI comparison

Amazon Web Services (AWS) and Travis CI are both solutions in the Build Automation category. Amazon Web Services (AWS) is ranked #9 with an average rating of 8.1, while Travis CI is ranked #21 with an average rating of 6.0. Amazon Web Services (AWS) holds a 1.2% mindshare in BA, compared to Travis CI’s 0.8% mindshare. Additionally, 90% of Amazon Web Services (AWS) users are willing to recommend the solution.

AWS CodeBuild

Read 11 AWS CodeBuild reviews

514 Views
300 Comparison Views

90% willing to recommend

Travis CI

Read 2 Travis CI reviews

402 Views
297 Comparison Views

0% willing to recommend

AWS CodeBuild

Travis CI

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Mar 5, 2025

Travis CI and AWS CodeBuild are prominent contenders in the CI/CD arena. AWS CodeBuild is often seen as more advantageous due to its comprehensive integration capabilities and scalability, justifying its pricing compared to Travis CI.

Features: Travis CI offers a simple setup and seamless GitHub integration, ideal for small to medium projects. It provides swift configuration, excellent test execution, and caters to developers looking for speed. AWS CodeBuild stands out with scalability, flexibility, and integration with AWS services like S3 and EC2. It supports continuous build and integration across multiple languages, which is beneficial for large-scale and complex projects.

Ease of Deployment and Customer Service: Travis CI provides an easy deployment model with a fast setup process and user-friendly support. AWS CodeBuild, part of the AWS ecosystem, offers comprehensive documentation and wide community support. However, it can present a steeper learning curve with its powerful resource characteristics.

Pricing and ROI: Travis CI offers competitive pricing, making it cost-effective for small to medium-sized projects with quick ROI. AWS CodeBuild's pricing reflects its expansive features and scalability, resulting in higher initial costs but potentially significant long-term ROI. Travis CI suits smaller project budgets, while AWS CodeBuild's features add value in larger projects.

To learn more, read our detailed Build Automation Report (Updated: June 2025).

Buyer's Guide

Build Automation

June 2025

Download the complete report

Helped 857,028 peers since 2012

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 CodeBuild

Ranking in Build Automation

9th

Average Rating

8.2

Reviews Sentiment

7.7

Number of Reviews

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

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of June 2025, in the Build Automation category, the mindshare of AWS CodeBuild is 1.2%, down from 1.5% compared to the previous year. The mindshare of Travis CI is 0.8%, down from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Munisaiteja Narravula

AWS Engineer at 6thgen

Automated task handling with reliable logging but requires accurate environment setup

One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors. It's crucial to have accurate environment configurations to avoid such problems. During the build stage, we often face time issues that cause delays, which can be troublesome.

Read full review

Pravar Agrawal

Senior SRE at IBM

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.

Read full review

Quotes from Members

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

Pros

"The initial setup of CodeBuild is easy."

"The integration with other AWS services has streamlined our workflow."

"It works seamlessly with AWS Elastic Container Registry (ECR)."

"The solution provides good integrations."

"CodeBuild supports various platforms and coding."

"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."

"The most important thing is that it's self-contained in an AWS account, and it's all linked to the customer's AWS account."

"AWS CodeBuild reduces wait time and optimizes workflows."

More AWS CodeBuild pros

"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."

Cons

"The deployment fails sometimes."

"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."

"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."

"Multiple clients have faced issues with pricing. After migrating from Azure to EC2, they were unexpectedly charged 100,000 rupees because the pricing details were not clearly visible."

"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."

"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."

"There is no persistent storage or preservation of workspace between the builds."

"Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds."

More AWS CodeBuild cons

"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."

Pricing and Cost Advice

"AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code."

"Despite the cost, it is worth the investment."

"We pay a monthly licensing fee."

Information not available

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

857,028 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Computer Software Company

17%

Financial Services Firm

13%

Manufacturing Company

11%

Media Company

10%

No data available

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

Questions from the Community

What do you like most about AWS CodeBuild?

It works seamlessly with AWS Elastic Container Registry (ECR).

See all answers

What is your experience regarding pricing and costs for AWS CodeBuild?

Issues with pricing have been mentioned, especially for new clients who might not realize the cost implications initially, such as leaving servers on for too long and incurring unexpectedly high bi...

See all answers

What needs improvement with AWS CodeBuild?

There is room for improvement in making AWS CodeBuild available on Windows servers in the Mumbai region. Multiple clients have faced issues with pricing. After migrating from Azure ( /products/micr...

See all answers

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.

See all answers

What needs improvement with Travis CI?

See all answers

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, ...

See all answers

Comparisons

GitHub Actions vs AWS CodeBuild

Compared 48% of the time

Jenkins vs AWS CodeBuild

Compared 31% of the time

GitLab vs AWS CodeBuild

Compared 21% of the time

More AWS CodeBuild Competitors

Tekton vs Travis CI

Compared 100% of the time

More Travis CI Competitors

Product Reports

Buyer's Guide

AWS CodeBuild

June 2025

Download AWS CodeBuild product report

Buyer's Guide

Build Automation

June 2025

Download Travis CI product report

Also Known As

CodeBuild

No data available

Overview

AWS CodeBuild is a fully managed continuous integration 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. CodeBuild scales continuously and processes multiple builds concurrently, so your builds are not left waiting in a queue. You can get started quickly by using prepackaged build environments, or you can create custom build environments that use your own build tools. With CodeBuild, you are charged by the minute for the compute resources you use.

Amazon Web Services (AWS)

Easily sync your GitHub projects with Travis CI and you'll be testing your code in minutes. Travis CI for private repositories has plans for every size project. With Travis CI testing your open source project is 100% free.

Travis CI

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, Jenkins and others in Build Automation. Updated: June 2025.

DOWNLOAD NOW

857,028 professionals have used our research since 2012.

See our list of best Build Automation vendors.

We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.