Knapsack Pro

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

Shippable

https://www.shippable.com

CodeShip

https://codeship.com
Unique feature

N/A

Runs on own infrastructure

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

Free for up to 100 builds per month

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, calculator, expensive

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

Offers great dev 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

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

Via easy Yaml config file, limited by the specs of the machine you have purchased

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.

No

Containers support / Build environment

Yes

Native Docker support

Yes

Native support for Docker

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

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

Yes

Yes

Full with organization and teams management

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

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

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

N/A

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

Fairly complete documentation on Ruby projects: https://documentation.codeship.com/pro/languages-frameworks/ruby/

Specific language support: JavaScript

Yes

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

Yes

Fairly complete documentation on Node.js projects: https://documentation.codeship.com/pro/languages-frameworks/nodejs/

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

Yes

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

Yes

Easy to integrate a bunch of 3rd party services, such as Code Climate, Codecov, Rancher, Pager Duty and many more: https://documentation.codeship.com/general/integrations/codeclimate/

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

Custom integrations are possible: https://documentation.codeship.com/general/integrations/custom-integration/

Auditing

Yes

N/A

Additional notes

CodeShip Pro gives you a lot more flexibility when defining your CI/CD process, plus you get your own AWS instance, so your build doesn't run on a shared server (this can be important for HIPAA or GDPR compliance, etc).

CodeShip Parallelisation - Parallel Test Pipelines how to run Ruby & JavaScript tests faster

CodeShip parallelism integration

Start using Knapsack Pro with Shippable or CodeShip

Sign up and speed up your tests.

Get started free