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

Cirrus CI

https://cirrus-ci.org

Solano CI

https://xebialabs.com/technology/solano-ci/
Unique feature

FreeBSD support

N/A

Type of product

SaaS / On Premise

N/A

Offers a free plan

Yes

Free for open source projects

No

Their website only mentions a free trial
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.

No

Very hard to get any information on pricing. It seems like they target enterprise clients only.
Support / SLA

N/A

Not clear if they offer any real SLA on support.

N/A

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

N/A

They mention that by paralellizing tests they get a huge performance boost (10x to 80x) but details are severly lacking.
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

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

The wording they use implies that this is possible.
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

N/A

Hosted plans / SaaS

Yes

N/A

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

Yes

The wording they use suggests that this is possible.
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

N/A

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

N/A

Probably not, considering how non-transparent this product is.
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.

N/A

Specific language support: JavaScript

No

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

N/A

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.

N/A

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

N/A

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)

It seems like Solano CI has been retired, and the new solution is the XebiaLabs DevOps Platform, but which integrates Jenkins and Travis, among others: https://xebialabs.com/products/devops-platform-overview/

How to run parallel tests on Cirrus CI and Solano CI
to execute 1-hour test suite 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



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 Solano CI server

  • save time & money
  • deliver features faster
  • catch errors earlier

Introduction to CI parallelisation with Knapsack Pro

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

How much can you save with faster tests
on Cirrus CI and Solano 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 Solano 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 Solano CI

Sign up and speed up your tests.