Knapsack Pro

Shippable vs Heroku CI comparison of Continuous Integration servers
What are the differences between Shippable and Heroku CI?

Shippable

https://www.shippable.com

Heroku CI

https://www.heroku.com/continuous-integration
Unique feature

N/A

Heroku Flow

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.

No (partial)

For CI only, the cost starts at $10 for pipeline, plus a variable amount depending on how long the build runs for (prorated per second). The servers used for CI cost $250 for a full month, which means you get about 3 hours for $1. For hosting, there's a free tier, limited to 1 web/1 worker with 512 MB RAM. One of the more annoying limitations is that free dynos are put into sleep mode after 30 min. of inactivity, which increases loading times considerably.

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

Clearly defined, offers a calculator.

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

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

Up to 16 nodes. You can ask Heroku support to enable up to 32 parallel dynos.

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.

N/A

Containers support / Build environment

Yes

Native Docker support

Yes

Builds run in isolation on new dynos (Heroku containers). Wide support via buildpacks: https://devcenter.heroku.com/articles/buildpacks

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

Great visual overview built-in.

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

Yes

Yes

One of the more mature solutions for teams on the market, Heroku Teams is available for free for 1-5 people, and comes at a cost for 6+ team members: https://www.heroku.com/pricing#team-comparison. Allows setting roles and app-level permissions with ease.

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

Very easy and intuitive process that allows defining a pipeline from code commit, to code review (review apps), user acceptance testing and production deployment, via Heroku Flow. Works best if the project is also hosted on Heroku.

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

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

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

Yes

Wide array of 3rd party add-ons available via Heroku Elements: https://elements.heroku.com/addons. Custom buildpacks are also available for almost any stack you might be using (over 5500 buildpacks available at the moment)

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

Although not specifically built in to Heroku, it's guaranteed that any Ruby specific need that might arise would be solved via add-ons, buildpacks or other integrations available.

Specific language support: JavaScript

Yes

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

Yes

Although not specifically built in to Heroku, it's guaranteed that any Javascript specific need that might arise would be solved via add-ons, buildpacks or other integrations available.

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

Yes

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

Yes

The strongest built-in integrations are with GitHub and Slack (ChatOps) but even allows integrating 3rd party CI servers in the workflow if you so require, among others.

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/

Yes

Offers a feature rich API that allows CRUD operations on the most important features, such as promoting an app to production, or inspecting a specific pipeline.

Auditing

Yes

Yes

Additional notes

How to leverage Heroku CI to run your tests faster?

Introduction to Knapsack Pro Heroku add-on

Heroku CI parallelism integration

Start using Knapsack Pro with Shippable or Heroku CI

Sign up and speed up your tests.

Get started free