Knapsack Pro

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

Github Actions

https://github.com/features/actions

Shippable

https://www.shippable.com
Unique feature

Best GitHub integration possible

N/A

Type of product

SaaS / On Premise

SaaS / On Premise

Offers a free plan

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.

Yes

Free unlimited builds for open source projects, 150 builds per month for all others (hosted plan). For the on-premise solution they only offer a 30 day trial.

Predictable pricing

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)

Yes

Clear pricing based on number of concurrent jobs. They also allow a varied combination of platforms you want to run (Ubuntu, Windows, MacOS, CentOS) and provide a Bring Your Own Node option (so you can run builds on your own infrastructure)

Support / SLA

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.

Yes

One of the few competitors to offer support tiers with clearly defined SLAs: https://www.shippable.com/premium-support.html as well as Services and Training: https://www.shippable.com/devops-services.html

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

Matrix builds allow concurrent jobs, even multi-platform.

Yes

One thing that stands out, is the shipctl CLI tool, which can automatically determine which tests to run in parallel, based on previous performance, such that a minimal amount of time is ensured: http://docs.shippable.com/ci/running-parallel-tests/#running-tests-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

No specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available.

N/A

No specific mention. From the wording, multiple environments are certainly available, but it's unclear if the tasks can be distributed to multiple containers/VMs on the same machine, or multiple machines.

Containers support / Build environment

Yes

Linux, macOS, Windows, and containers, or run directly in a VM.

Yes

Native Docker support

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

Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes.

Yes

Detailed statistics available at multiple levels (job, account, project, etc.). They also include a view they call SPOG (Single Pane of Glass) which allows viewing a real-time representation of all of the pipelines in the organization, from where you can drill-in to the leaf nodes you're interested in.

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

N/A

Unclear from the available documentation

Yes

Self-hosted option

Yes

Coming soon, not available yet.

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

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)

Yes

Configurable via an YML file (called Assembly Lines)

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

Unclear from the available documentation

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?

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

Yes

https://www.shippable.com/integrations.html

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

Unclear how, but they mention Ruby support specifically on the homepage

Yes

Ruby is available by default on the Shippable container images. They also provide support for tools such as Cucumber or RSpec. Specific documentation for Ruby available on the website: http://docs.shippable.com/ci/ruby-continuous-integration/

Specific language support: JavaScript

Yes

Unclear how, but they mention Javascript (Node.js) support specifically on the homepage

Yes

Specific documentation for Node.js available: http://docs.shippable.com/ci/ruby-continuous-integration/

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

Yes

Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more)

Yes

http://docs.shippable.com/ci/ruby-continuous-integration/

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

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)

Yes

Provides a straight-forward REST API: http://docs.shippable.com/platform/api/api-overview/. They also provide ways to integrate notifications in your workflow, via webhooks or specific channels (IRC, Slack, Email, etc): http://docs.shippable.com/ci/send-notifications/

Auditing

N/A

Yes

Additional notes

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

Start using Knapsack Pro with Github Actions or Shippable

Sign up and speed up your tests.

Get started free