AWS CodeBuild vs Jenkins vs Travis CI

Overview

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

AWS CodeBuild

Stacks443

Followers485

Votes43

AWS CodeBuild vs Jenkins vs Travis CI: What are the differences?

Cost: One key difference between AWS CodeBuild and Jenkins and Travis CI is the cost. AWS CodeBuild charges per minute for build time, while Jenkins and Travis CI are open source tools and do not have any direct cost associated with them. This means that AWS CodeBuild may be more expensive for large-scale projects compared to Jenkins and Travis CI.
Scalability: Another difference is the scalability. AWS CodeBuild can easily scale up or down based on the demand and can handle large build volumes efficiently. On the other hand, Jenkins and Travis CI are limited by the resources available on the server they are installed on, which may lead to performance issues when dealing with large projects or high build volumes.
Integration with AWS Services: AWS CodeBuild seamlessly integrates with other AWS services like AWS CodeCommit, AWS CodePipeline, and AWS Elastic Beanstalk. This allows for tighter integration and streamlined workflows within the AWS ecosystem. Jenkins and Travis CI, while they have plugins and integrations available, may require additional configuration and setup to achieve similar levels of integration.
Ease of Use: AWS CodeBuild provides a simple and intuitive web interface for configuring build projects. It allows for easy setup and management of build environments using preconfigured build images or custom build environments. Jenkins and Travis CI, on the other hand, require installation and configuration on a server, which may involve more technical expertise and maintenance.
Flexibility: AWS CodeBuild offers a wide range of options for build environments and customizations, including the ability to use Docker containers for builds. This provides flexibility in choosing the desired environment and tools for the build process. Jenkins and Travis CI also offer customization options, but they may require more manual configuration and setup compared to AWS CodeBuild.
Managed Service vs Self-Hosted: AWS CodeBuild is a managed service provided by Amazon, meaning that the infrastructure and maintenance are handled by AWS. This removes the need for self-hosting and server management. In contrast, Jenkins and Travis CI are self-hosted tools, which requires setup, maintenance, and monitoring of the server infrastructure.

In Summary, AWS CodeBuild offers a cost-effective and scalable solution with seamless integration with other AWS services, while Jenkins and Travis CI provide more flexibility and control but require additional configuration and maintenance.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Travis CI, Jenkins, AWS CodeBuild

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

Comments

Felipe

May 24, 2020

Needs advice

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.

198k views198k

Comments

StackShare

Apr 17, 2019

Needs advice

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?"

529k views529k

Comments

Detailed Comparison

Travis CI	Jenkins	AWS CodeBuild
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.	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 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’t need to provision, manage, and scale your own build servers.
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.	Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support	Fully Managed Build Service;Continuous Scaling;Enables Continuous Integration;Integrates seamlessly with AWS services;FAQs: https://aws.amazon.com/codebuild/faqs/
Statistics
GitHub Stars -	GitHub Stars 24.6K	GitHub Stars -
GitHub Forks -	GitHub Forks 9.2K	GitHub Forks -
Stacks 28.0K	Stacks 59.2K	Stacks 443
Followers 6.7K	Followers 50.4K	Followers 485
Votes 1.7K	Votes 2.2K	Votes 43
Pros & Cons
Pros 506 Github integration 388 Free for open source 271 Easy to get started 191 Nice interface 162 Automatic deployment Cons 8 Can't be hosted insternally 3 Unstable 3 Feature lacking 2 Incomplete documentation for all platforms	Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Limited abilities with declarative pipelines 7 Lack of support	Pros 7 Pay per minute 5 Parameter Store integration for passing secrets 4 Integrated with AWS 3 Bit bucket integration 3 Streaming logs to Amazon CloudWatch Cons 2 Poor branch support
Integrations
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	No integrations available	AWS Elastic Beanstalk AWS CodeCommit Amazon S3 GitHub Bitbucket AWS CloudFormation GitHub Enterprise

What are some alternatives to Travis CI, Jenkins, AWS CodeBuild?

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

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.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Appveyor

AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.

Related Comparisons

AWS CodeBuild vs Jenkins vs Travis CI: What are the differences?

Cost: One key difference between AWS CodeBuild and Jenkins and Travis CI is the cost. AWS CodeBuild charges per minute for build time, while Jenkins and Travis CI are open source tools and do not have any direct cost associated with them. This means that AWS CodeBuild may be more expensive for large-scale projects compared to Jenkins and Travis CI.
Scalability: Another difference is the scalability. AWS CodeBuild can easily scale up or down based on the demand and can handle large build volumes efficiently. On the other hand, Jenkins and Travis CI are limited by the resources available on the server they are installed on, which may lead to performance issues when dealing with large projects or high build volumes.
Integration with AWS Services: AWS CodeBuild seamlessly integrates with other AWS services like AWS CodeCommit, AWS CodePipeline, and AWS Elastic Beanstalk. This allows for tighter integration and streamlined workflows within the AWS ecosystem. Jenkins and Travis CI, while they have plugins and integrations available, may require additional configuration and setup to achieve similar levels of integration.
Ease of Use: AWS CodeBuild provides a simple and intuitive web interface for configuring build projects. It allows for easy setup and management of build environments using preconfigured build images or custom build environments. Jenkins and Travis CI, on the other hand, require installation and configuration on a server, which may involve more technical expertise and maintenance.
Flexibility: AWS CodeBuild offers a wide range of options for build environments and customizations, including the ability to use Docker containers for builds. This provides flexibility in choosing the desired environment and tools for the build process. Jenkins and Travis CI also offer customization options, but they may require more manual configuration and setup compared to AWS CodeBuild.
Managed Service vs Self-Hosted: AWS CodeBuild is a managed service provided by Amazon, meaning that the infrastructure and maintenance are handled by AWS. This removes the need for self-hosting and server management. In contrast, Jenkins and Travis CI are self-hosted tools, which requires setup, maintenance, and monitoring of the server infrastructure.

AWS CodeBuild vs Jenkins vs Travis CI

Overview