Knapsack Pro

Buildkite vs Travis CI comparison of Continuous Integration servers
What are the differences between Buildkite and Travis CI?

Buildkite

https://buildkite.com

Travis CI

https://travis-ci.org
Unique feature

Runs on own infrastructure, API

Build Matrix, ease of use, GitHub integration

Type of product

SaaS

SaaS, Self-hosted / On Premise

Offers a free plan

Yes

Free for open source projects and selected organizations

Yes

Free for open source projects

Predictable pricing

Yes

Clearly defined monthly and annual plans

Yes

Clearly defined monthly plans, depending on concurrent jobs needed.

Support / SLA

Yes

Depending on the plan, ranging from community support, all the way to an assigned Technical Manager, SLAs and live chat support.

Yes

Available via email, or dedicated online interface for paid plans.

Paralellism
Every CI servers tends to address this differently (parallel, distributed, build matrix). Some of it is just marketing, and some is just nuance. For this table, parallel means that tasks can be run concurrently on the same machine, distributed means that tasks can be scaled horizontally, on multiple machines
How to split tests in parallel in the optimal way with Knapsack Pro

Yes

Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs. You can run your tests in isolated Docker container per agent.

Yes

TravisCI makes it very easy to split your build into different stages which are then run in parallel (ie: run integration tests separate from the unit tests). TravisCI calls this a build matrix: https://docs.travis-ci.com/user/build-matrix/. You can also very easily split tests accross several VMs using the knapsack_pro gem.

Distributed builds
distributed means that tasks can be scaled horizontally, on multiple machines
How to split tests in parallel in the optimal way with Knapsack Pro

Yes

Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs

N/A

Containers support / Build environment

Yes

Since the agents run on your own infra, you're free to do whatever

Yes

TravisCI runs each build in a isolated virtual machine. Pre-build packages include a few which support specific languages (Ruby and JavaScript included) or other software (Git, various databases), but vanilla packages such as Ubuntu Trusty are also available.

Analytics / Status overview
Analytics and overview referrs to the ability to, at a glance, see what's breaking (be it a certain task, or the build for a specific project)

Yes

The Buildkite UI features great vizualisations that feature build times, error rates, and more.

Yes

Available by default in Travis (this is what most of the web UI consists of)

Management support
How easy is it to manage users / projects / assign roles and permissions and so on

Yes

N/A

Self-hosted option

No

Yes

Hosted plans / SaaS

Yes

Yes

Build pipelines
A continuous delivery pipeline is a description of the process that the software goes through from a new code commit, through testing and other statical analysis steps all the way to the end-users of the product.

Yes

Pipelines are defined using an Yaml config file and allow for great flexibility in defining what each step of the process does.

No

Specifically built around GitHub pull requests. Pipelines can be defined, but parts of the process need to be implemented separatelly in GitHub.

Reports
Reports are about the abilty to see specific reports (like code coverage or custom ones), but not necesarily tied in into a larger dashboard.

Yes

Yes (partial)

No persistent storage eliminates the possibility of code coverage reports on TravisCI alone. There is support for integrated 3rd parties such as Coveralls for reporting code coverage.

Ecosystem
Besides the official documentation and software, is there a large community using this product? Are there any community-driven tools / plugins that you can use?

Yes

Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API). Growing number of community plugins: https://buildkite.com/plugins

No plugin support in TravisCI, plugins for other tools

Specific language support: Ruby
Some CI servers have built-in support for parsing RSpec or Istanbul output for example and we mention those. Some others make it even easier by detecting Gemfiles or package.json and automate parts of the process for the developer.

Yes

You can find useful plugins like https://github.com/sj26/rspec-buildkite https://github.com/ticky/simplecov-buildkite etc

Yes

TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Ruby, starting from pre-built containers (with RVM already installed, for example) all the way to automatically running specific platform commands (such as detecting a Gemfile in the root of the project and automatically bundling dependencies). TravisCI also builds a Ruby SDK for easier use of the API.

Specific language support: JavaScript

No

Yes

TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Javascript, starting from pre-built containers (with node already installed, for example) all the way to automatically running specific platform commands (such as detecting a package.json in the root of the project and running npm test)

Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc)

Yes

Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API)

Yes

By default, TravisCI is built to work with GitHub. Additionally, there is strong support for 3rd party tools like Coveralls, BrowserStack, etc.

API
Custom integreation is available, via an API or otherwise, it's mentioned separately as it allows further customization than any of the Ecosystem/Integration options

Yes

Great GraphQL API, allows building your own dashboard with ease

Yes

Offers a feature-rich API that allows both reading data, as well as triggering or cancelling builds.

Auditing

Yes

N/A

Additional notes

Buildkite parallel agents and how to use them for CI parallelisation

Travis CI build matrix feature how to use it for CI parallelisation

Buildkite parallelism integration

Travis CI parallelism integration

Start using Knapsack Pro with Buildkite or Travis CI

Sign up and speed up your tests.

Get started free