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

AWS CodePipeline

379
642
+ 1
30
Travis CI

7.5K
5.2K
+ 1
1.8K
Add tool

AWS CodePipeline vs Travis CI: What are the differences?

Developers describe AWS CodePipeline as "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. On the other hand, Travis CI is detailed as "A hosted continuous integration service for open source and private projects". Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

AWS CodePipeline and Travis CI 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, Travis CI provides the following key features:

  • Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.
  • Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.
  • Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.

"Simple to set up" is the top reason why over 3 developers like AWS CodePipeline, while over 505 developers mention "Github integration" as the leading cause for choosing Travis CI.

Lyft, Heroku, and MIT are some of the popular companies that use Travis CI, whereas AWS CodePipeline is used by Volta Industries, ChromaDex, and PouchNATION. Travis CI has a broader approval, being mentioned in 666 company stacks & 613 developers stacks; compared to AWS CodePipeline, which is listed in 30 company stacks and 15 developer stacks.

Advice on AWS CodePipeline and Travis CI
Needs advice
on
Jenkins
Travis CI
and
CircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Developer at Elegant Themes | 13 upvotes 路 188K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit | 9 upvotes 路 165.8K views
Recommends
Travis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
Travis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
GitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
Buildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
View all (6)
Decisions about AWS CodePipeline and Travis CI

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container. Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website. This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

See more

We were long time users of TravisCI, but switched to CircleCI because of the better user interface and pricing. Version 2.0 has had a couple of trips and hiccups; but overall we've been very happy with the continuous integration it provides. Continuous Integration is a must-have for building software, and CircleCI continues to surprise as they roll out ideas and features. It's leading the industry in terms of innovation and new ideas, and it's exciting to see what new things they keep rolling out.

See more

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AWS CodePipeline
Pros of Travis CI
  • 13
    Simple to set up
  • 8
    Managed service
  • 4
    GitHub integration
  • 3
    Parallel Execution
  • 2
    Automatic deployment
  • 0
    Manual Steps Available
  • 508
    Github integration
  • 388
    Free for open source
  • 272
    Easy to get started
  • 191
    Nice interface
  • 163
    Automatic deployment
  • 72
    Tutorials for each programming language
  • 40
    Friendly folks
  • 29
    Support for multiple ruby versions
  • 28
    Osx support
  • 24
    Easy handling of secret keys
  • 6
    Fast builds
  • 4
    Support for students
  • 3
    The best tool for Open Source CI
  • 3
    Hosted
  • 3
    Build Matrices
  • 2
    Straightforward Github/Coveralls integration
  • 2
    Easy of Usage
  • 2
    Github Pull Request build
  • 2
    Integrates with everything
  • 1
    Docker support
  • 1
    Configuration saved with project repository
  • 1
    Free for students
  • 1
    Build matrix
  • 1
    No-brainer for CI
  • 1
    Debug build workflow
  • 1
    Great Documentation
  • 1
    Multi-threaded run
  • 1
    Hipchat Integration
  • 1
    Caching resolved artifacts
  • 1
    Ubuntu trusty is not supported
  • 0
    Perfect
  • 0
    One

Sign up to add or upvote prosMake informed product decisions

Cons of AWS CodePipeline
Cons of Travis CI
  • 2
    No project boards
  • 1
    No integration with "Power" 365 tools
  • 8
    Can't be hosted insternally
  • 3
    Feature lacking
  • 3
    Unstable
  • 2
    Incomplete documentation for all platforms

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 Travis CI?

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

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

What companies use AWS CodePipeline?
What companies use Travis CI?
See which teams inside your own company are using AWS CodePipeline or Travis CI.
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 Travis CI?

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

Blog Posts

What are some alternatives to AWS CodePipeline and Travis CI?
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鈥檛 need to provision, manage, and scale your own build servers.
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.
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.
See all alternatives
Reviews of AWS CodePipeline and Travis CI
Review of
Travis CI

In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!

How developers use AWS CodePipeline and Travis CI
datapile uses
Travis CI

Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.

It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).

Dieter Adriaenssens uses
Travis CI

Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.

Nate Ferrell uses
Travis CI

Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.

Andrew Williams uses
Travis CI

To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

Sascha Manns uses
Travis CI

Travis provides more than one Ruby version setting. So i can test my push directly in different Ruby versions.