Scrutinizer CI vs Github Actions comparison of Continuous Integration servers

	Scrutinizer CI https://scrutinizer-ci.com	Github Actions https://github.com/features/actions
Unique feature	Ongoing statical analysis	Best GitHub integration possible
Type of product	SaaS	SaaS / On Premise
Offers a free plan	Yes Free for open source projects	Yes The on premise plan (not yet available) will be free, 2000 build minutes included in the free cloud plan. Completely free plan for open source projects.
Predictable pricing	Yes Three different paid monthly tiers	Yes (partial) While it's clear what the cost is (priced per build-minute), figuring out costs can be a hassle, especially as the price can vary quite a bit depending on commits to the project. One advantage for GitHub Actions is that the tiers define a maximum amount of minutes, so it's easier to predict the final cost. You can also purchase aditional runners with pricing dependent on the platform (MacOS, Linux, Windows)
Support / SLA	N/A Not specifically mentioned, probably not.	Yes Community support available for any tier, unclear at what point and if dedicated support is available. Safe to assume that eneterprise clients can access technical support.
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 Automated parallalelization for code analysis, as well as support for running tasks in parallel	Yes Matrix builds allow concurrent jobs, even multi-platform.
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 Unclear from the documentation (probably not)	N/A No specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available.
Containers support / Build environment	Yes Tests run in isolated containers. Docker support available.	Yes Linux, macOS, Windows, and containers, or run directly in a VM.
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 Besides classic CI overview, they also provide static code analysis insights, which is a differentiator for Scrutinizer	Yes Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes.
Management support How easy is it to manage users / projects / assign roles and permissions and so on	Yes Additional seats available for every plan at $14.90 per seat, per month.	N/A Unclear from the available documentation
Self-hosted option	No	Yes Coming soon, not available yet.
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 as code (YML files)	Yes Called GitHub Action Workflows, they are defined in separate Docker containers, using the YAML syntax (they used to support HCL, but they're migrating away from that)
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	N/A Unclear from the available documentation
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?	No	Yes Thanks to the large following, GitHub Actions already enjoys a wide varierty of available pre-made workflows, which you can browse right on the homepage: https://github.com/features/actions
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 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/	Yes Unclear how, but they mention Ruby support specifically on the homepage
Specific language support: JavaScript	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.	Yes Unclear how, but they mention Javascript (Node.js) support specifically on the homepage
Integrations 1st party support for common tools (like Slack notifications, various VCS platforms, etc)	Yes Light integration with third party systems, mainly code management frameworks like GitHub, Bitbucket, GitLab.	Yes Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more)
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 Comprehensive REST API available: https://scrutinizer-ci.com/docs/api/	N/A Unclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available)
Auditing	N/A Unclear from the documentation, but most likely available.	N/A
Additional notes	The code analysis features seem great, the offer for similar tools is quite light. Seems similar to lgtm.com

Programming Language	Supported test runners	Installation guide	Knapsack Pro Library README / Source
Ruby	RSpec, Cucumber, Minitest, test-unit, Spinach, Turnip	Install	knapsack_pro gem
JavaScript	Cypress.io	Install	@knapsack-pro/cypress
JavaScript	Jest	Install	@knapsack-pro/jest
JavaScript / TypeScript	Any test runner in JavaScript	How to build native integration with Knapsack Pro API to run tests in parallel for any test runner	@knapsack-pro/core
Any programming language	Any test runner	How to build a custom Knapsack Pro API client from scratch in any programming language	-

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

Scrutinizer CI

Github Actions

Ongoing statical analysis

Best GitHub integration possible

SaaS

SaaS / On Premise

Yes

Yes

Yes

Yes (partial)

N/A

Yes

Yes

Yes

N/A

N/A

Yes

Yes

Yes

Yes

Yes

N/A

No

Yes

Yes

Yes

Yes

Yes

Yes

N/A

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

N/A

N/A

N/A

How to run parallel tests on Scrutinizer CI and Github Actions to execute 1-hour test suite in 2 minutes?

Without Knapsack Pro

Run fast parallel CI build with Knapsack Pro

How it works

How to install it

Do you know

Start using Knapsack Pro

Sign up and speed up your tests.

Get faster feedback from Scrutinizer CI and Github Actions server

GitHub Actions testing Ruby on Rails with RSpec and parallel jobs (matrix feature)

How to run Jest tests on GitHub Actions - JS parallel jobs with matrix feature (NodeJS YAML config)

GitHub Actions Cypress.io E2E testing parallel jobs with matrix feature (NodeJS YAML config)

Github Actions parallelism integration

Introduction to CI parallelisation with Knapsack Pro

How much can you save with faster tests on Scrutinizer CI and Github Actions?

Features that make your tests perform better

Queue mode see video

Fallback mode

All supported test runners

Trusted solution

Start using Knapsack Pro with Scrutinizer CI or Github Actions

Sign up and speed up your tests.

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

How to run parallel tests on Scrutinizer CI and Github Actions
to execute 1-hour test suite in 2 minutes?

How much can you save with faster tests
on Scrutinizer CI and Github Actions?