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

Cirrus CI

https://cirrus-ci.org

Travis CI

https://travis-ci.org
Unique feature

FreeBSD support

Build Matrix, ease of use, GitHub integration

Type of product

SaaS / On Premise

SaaS, Self-hosted / On Premise

Offers a free plan

Yes

Free for open source projects

Yes

Free for open source projects
Predictable pricing

Yes

Besides the seat (per-user access) you need to buy compute credits for running the build, priced differently depending on the machine you're running builds on.

Yes

Clearly defined monthly plans, depending on concurrent jobs needed.
Support / SLA

N/A

Not clear if they offer any real SLA on 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 optimal way with Knapsack Pro

Yes

There are limits on how many tasks can be run in parallel for the free tier builds: https://cirrus-ci.org/faq/#are-there-any-limits

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 optimal way with Knapsack Pro

N/A

N/A

Containers support / Build environment

Yes

Allows containers or VMs for every major operating system.

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

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

N/A

N/A

Self-hosted option

Yes

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

Defined via YML config files

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.

N/A

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?

N/A

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.

No (partial)

No specific support from what I can gather, but it does provide documentation for Ruby, including integration with the knapsack_pro gem.

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

No specific support and no documentation on setting up a CI/CD process for a Javascript project.

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

Integrates well with GitHub - the whole CI/CD process starts with a commit to a GitHub repo.

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

Provides a pretty nifty GraphQL API which allows querying the Cirrus CI Schema, as well as webhooks support for other types of custom integrations (such as Slack or IRC notifications, for example). They also added support for GitHub actions

Yes

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

N/A

From what we can tell, there's no specific support for auditing changes in the Cirrus CI config (other than what is traceable via git commits to the YML config file)

N/A

Additional notes

Seems to be used by companies with a solid engineering background (Google)

How to run parallel tests on Cirrus CI and Travis CI
to execute 1-hour test suite in 2 minutes?

Without Knapsack Pro

you have to wait 20 minutes for slow tests running too long on red node

Loading...

Run fast parallel CI build with Knapsack Pro

CI build completes work in only 10 minutes because Knapsack Pro ensures all parallel nodes finish work at a similar time

Loading...

You can even run 20 parallel nodes to complete your CI build in 2 minutes

How it works

1. Install Knapsack Pro client in your project


2. Add Knapsack Pro client to your current CI server and run your tests in parallel

Knapsack Pro how it works with CI server

3. Update your CI server config file to run tests in parallel with Knapsack Pro

Knapsack Pro in Queue Mode will split tests in a dynamic way across parallel CI nodes to ensure each CI node finish work at a similar time. Thanks to that your CI build time is as fast as possible. It works with many supported CI servers.

Do you know

Start using Knapsack Pro

Sign up and speed up your tests.

Get faster feedback from Cirrus CI and Travis CI server

  • save time & money
  • deliver features faster
  • catch errors earlier
Knapsack Pro terminal

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

Travis CI parallelism integration

Introduction to CI parallelisation with Knapsack Pro

Run tests in parallel on Cirrus CI and Travis CI in optimal way and avoid bottleneck parallel jobs.

How much can you save with faster tests
on Cirrus CI and Travis CI?

minutes
$

Monthly you can save hours
and up to $
on faster development cycle.

Features that make your tests perform better

  • Queue mode see video

    Dynamic tests allocation across Cirrus CI and Travis CI parallel jobs. Autobalance tests to get optimal test suite split betweeen CI nodes.

  • Regular mode see video

    Test suite split based on time execution. Generates subset of test suite per CI node before running tests.

  • Fallback mode

    Network issues? Not a problem, run tests anyway! Auto switch to the fallback mode to not depend on Knapsack Pro API.

  • All supported test runners

    Ruby: RSpec, Minitest, Test::Unit, Cucumber, Spinach, Turnip.

    JavaScript: Cypress.io, Jest

    Do you use different programming language or test runner? Let us know in the poll

Discover all features or see
how to use Knapsack Pro with your CI

Trusted solution

Join the teams optimizing their tests with Knapsack Pro.

We've been really enjoying Knapsack Pro, it's been saving us a ton of time.

Devin Brown Software Engineer at Pivotal

This is a fantastic product, it's been a total game-changer for us.

Geoff Harcourt CTO at CommonLit

We are using CircleCI and we noticed that builds were being limited by the slowest parallelized container. Knapsack Pro was really east to setup and we saw huge improvements right away. Thank you for making this tool!

Martin Sieniawski Software Engineer at Collage

Knapsack Pro has helped us build an insanely fast and scaleable build pipeline with almost no setup or maintenance.

Tim Lucas Co-founder of buildkite.com

Knapsack Pro saves us hours of engineer waiting time every week, and is the best solution for keeping our tests load balanced that we've used to date.

Michael Amygdalidis Senior Software Engineer at Popular Pays

I've been playing with Queue Mode. Love it! Wow, I love how fast it goes.

Michael Menne CTO at humanagency.org

I just logged into my account expecting it to say that I needed to add a credit card and was so surprised and delighted to see the trial doesn't count usage by calendar days but by testing days! This is incredible! I love it!!!

I just wanted to say that I really appreciate that small but very huge feature. Thank you for being so thoughtful :)

Shannon Baffoni Senior Software Engineer
at Blue Bottle Coffee

See more testimonials

Start using Knapsack Pro with Cirrus CI or Travis CI

Sign up and speed up your tests.