Knapsack Pro

Shippable vs Netlify Build comparison of Continuous Integration servers
What are the differences between Shippable and Netlify Build?

Shippable

https://www.shippable.com

Netlify Build

https://www.netlify.com/products/build/
Unique feature

N/A

Deploy your sites to global Netlify infrastructure

Every commit gets its own deployed version. Automatically attach a new Deploy Preview at a unique permanent URL whenever you submit a Pull/Merge Request. Set Netlify Build to deploy every branch in the repository for unlimited staging environments.

Type of product

SaaS / On Premise

SaaS

Offers a free plan

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.

Yes

300 build minutes/month, 1 concurrent CI build

Predictable pricing

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)

Yes

Extra 500 build minutes costs $7/month. User seat $15/user/month.

Support / SLA

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

Yes

99.99% uptime SLA for Starter and Pro plan. Business plan has negotiable SLA.

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

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

Yes

Starter plan (free) has only 1 concurrent build but Pro plan has 3 concurrent builds included.

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. 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.

Yes

High-Performance Builds - The premium build environment gives more concurrency, processing power and asynchronous deploys.

Containers support / Build environment

Yes

Native Docker support

Yes

When you trigger a build on Netlify, their buildbot starts a Docker container to build your website. The buildbot will look for instructions about required languages and software needed to run your command before running build command. The instructions are called dependencies, and how you declare them depends on the programming languages and tools used in build. Build image selection is available. Until recently, all Netlify sites were built using the same build image. Netlify is experimenting with allowing customers to select from multiple Docker images with different operating systems and software versions.

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

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.

Yes

Simple dashboard to see CI builds. Other than CI analytics Netlify has Netlify Analytics that brings data captured directly from their servers for your website.

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

Yes

Yes

Team members managment. Role-based access control only in business plan.

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

Configurable via an YML file (called Assembly Lines)

Yes, partially

Simple steps, define your own steps in bash commands

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

No

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

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

No

There are only small helpful things like incoming webhooks so other services can trigger Netlify deploys, and send outgoing webhooks as a deploy starts, succeeds, or fails.

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

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/

Yes

It has support for Ruby.

Specific language support: JavaScript

Yes

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

Yes

It has support for JavaScript.

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

Yes

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

Yes

Netlify has incoming webhooks so other services can trigger Netlify deploys, and send outgoing webhooks as a deploy starts, succeeds, or fails. For instance you can integrate it with Slack.

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 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/

No

Auditing

Yes

N/A

Additional notes

Start using Knapsack Pro with Shippable or Netlify Build

Sign up and speed up your tests.

Get started free