Knapsack Pro

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

Cirrus CI

https://cirrus-ci.org

Scrutinizer CI

https://scrutinizer-ci.com
Unique feature

FreeBSD support

Ongoing statical analysis

Type of product

SaaS / On Premise

SaaS

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

Three different paid monthly tiers

Support / SLA

N/A

Not clear if they offer any real SLA on support.

N/A

Not specifically mentioned, probably not.

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

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

Automated parallalelization for code analysis, as well as support for running tasks in parallel

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

N/A

N/A

Unclear from the documentation (probably not)

Containers support / Build environment

Yes

Allows containers or VMs for every major operating system.

Yes

Tests run in isolated containers. Docker support 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

Besides classic CI overview, they also provide static code analysis insights, which is a differentiator for Scrutinizer

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

N/A

Yes

Additional seats available for every plan at $14.90 per seat, per month.

Self-hosted option

Yes

No

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

Yes

Pipelines as code (YML files)

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

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

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

Code analysis (automated code reviews) are available for Ruby, as well as specific documentation for setting up a Ruby project: https://scrutinizer-ci.com/docs/guides/ruby. Frameworks like Ruby on Rails are supported. They also provide tools like bundler-audit, for identifying vulnerable gems: https://scrutinizer-ci.com/docs/tools/ruby/bundler-audit/

Specific language support: JavaScript

No

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

Yes

Automated code reviews are available for Javascript as well as specific documentation for setting up a Node.js project: https://scrutinizer-ci.com/docs/guides/javascript. Typescript is also supported.

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

Light integration with third party systems, mainly code management frameworks like GitHub, Bitbucket, GitLab.

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

Comprehensive REST API available: https://scrutinizer-ci.com/docs/api/

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

Unclear from the documentation, but most likely available.

Additional notes

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

The code analysis features seem great, the offer for similar tools is quite light. Seems similar to lgtm.com

Start using Knapsack Pro with Cirrus CI or Scrutinizer CI

Sign up and speed up your tests.

Get started free