Knapsack Pro

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

CodeShip

https://codeship.com

Rancher Pipelines

https://rancher.com/docs/rancher/v2.x/en/project-admin/tools/pipelines/
Unique feature

Runs on own infrastructure

DevOps tool for container orchestration

Type of product

SaaS

On Premise

Offers a free plan

Yes

Free for up to 100 builds per month

Yes

Free, open source project

Predictable pricing

Yes

Clearly defined, calculator, expensive

Yes

It's free!

Support / SLA

Yes

Offers great dev support

Yes

Paid support available: https://rancher.com/pricing/

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

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

Yes

You can run multiple parallel steps within a build stage

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

No

N/A

Unclear from the documentation (probably not)

Containers support / Build environment

Yes

Native support for Docker

Yes

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

Yes

Not particularly clear, but it appears you can monitor stats in a Grafana dashboard: https://rancher.com/docs/rancher/v2.x/en/project-admin/tools/monitoring/

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

Yes

Full with organization and teams management

Yes

User management is available, with specific roles assigned, or permissions to certain resources and projects

Self-hosted option

No

Yes

Hosted plans / SaaS

Yes

No

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

Yes

Pipelines as code (YML files), but also manageable via the UI

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

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?

N/A

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

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

N/A

Pipelines / CI is just a small part of Rancher. No specific support mentioned.

Specific language support: JavaScript

Yes

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

N/A

Pipelines / CI is just a small part of Rancher. No specific support mentioned.

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

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/

Yes

Integrations available for GitLab, GitHub and Bitbucket

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

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

Yes

REST API available. It provides introspection and documentation: https://github.com/rancher/api-spec/blob/master/specification.md#filtering. It should offer enough access to allow building whatever customizations or integrations with 3rd party tools deemed necessary.

Auditing

N/A

Yes

Allows logging to various systems (Kafka, Elastic, etc) which should make audit possible

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

Rancher is a full software stack for container orchestration, going as far as building their own Linux distribution (RancherOS). Using Rancher seems more like a decision to be made considering all other features Rancher offers, not just the CI server. Also worth noting that Rancher uses Jenkins under the hood, but the engine is locked so projects can't just be migrated between the two.

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

CodeShip parallelism integration

Start using Knapsack Pro with CodeShip or Rancher Pipelines

Sign up and speed up your tests.

Get started free