Knapsack Pro

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

Cirrus CI

https://cirrus-ci.org

CodeShip

https://codeship.com
Unique feature

FreeBSD support

Runs on own infrastructure

Type of product

SaaS / On Premise

SaaS

Offers a free plan

Yes

Free for open source projects

Yes

Free for up to 100 builds per month

Predictable pricing

Yes

Besides the seat (per-user access) you need to buy compute credits for running the build, priced differently depending on the machine you're running builds on.

Yes

Clearly defined, calculator, expensive

Support / SLA

N/A

Not clear if they offer any real SLA on support.

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

There are limits on how many tasks can be run in parallel for the free tier builds: https://cirrus-ci.org/faq/#are-there-any-limits

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

Containers support / Build environment

Yes

Allows containers or VMs for every major operating system.

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

Yes

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

N/A

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

Defined via YML config files

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.

N/A

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?

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.

No (partial)

No specific support from what I can gather, but it does provide documentation for Ruby, including integration with the knapsack_pro gem.

Yes

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

Specific language support: JavaScript

No

No specific support and no documentation on setting up a CI/CD process for a Javascript project.

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

Integrates well with GitHub - the whole CI/CD process starts with a commit to a GitHub repo.

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 pretty nifty GraphQL API which allows querying the Cirrus CI Schema, as well as webhooks support for other types of custom integrations (such as Slack or IRC notifications, for example). They also added support for GitHub actions

Yes

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

Auditing

N/A

From what we can tell, there's no specific support for auditing changes in the Cirrus CI config (other than what is traceable via git commits to the YML config file)

N/A

Additional notes

Seems to be used by companies with a solid engineering background (Google)

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 Cirrus CI or CodeShip

Sign up and speed up your tests.

Get started free