Knapsack Pro
Knapsack Pro
CodeShiphttps://codeship.com |
Cirrus CIhttps://cirrus-ci.org |
|
|---|---|---|
| Unique feature |
Runs on own infrastructure
|
FreeBSD support
|
| Type of product |
SaaS
|
SaaS / On Premise
|
| Offers a free plan |
Yes Free for up to 100 builds per month |
Yes Free for open source projects |
| Predictable pricing |
Yes Clearly defined, calculator, expensive |
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. |
| Support / SLA |
Yes Offers great dev support |
N/A Not clear if they offer any real SLA on 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 Via easy Yaml config file, limited by the specs of the machine you have purchased |
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 |
|
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
|
| Containers support / Build environment |
Yes Native support for Docker |
Yes Allows containers or VMs for every major operating system. |
|
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 |
Yes Full with organization and teams management |
N/A
|
| Self-hosted option |
No
|
Yes
|
| 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
|
Yes Defined via YML config files |
|
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. |
Yes Fairly complete documentation on Ruby projects: https://documentation.codeship.com/pro/languages-frameworks/ruby/ |
No (partial) No specific support from what I can gather, but it does provide documentation for Ruby, including integration with the knapsack_pro gem. |
| Specific language support: JavaScript |
Yes Fairly complete documentation on Node.js projects: https://documentation.codeship.com/pro/languages-frameworks/nodejs/ |
No No specific support and no documentation on setting up a CI/CD process for a Javascript project. |
|
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 Integrates well with GitHub - the whole CI/CD process starts with a commit to a GitHub repo. |
|
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 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 |
| Auditing |
N/A
|
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) |
| 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). |
Seems to be used by companies with a solid engineering background (Google) |