Knapsack Pro
Knapsack Pro
Rancher Pipelineshttps://rancher.com/docs/rancher/v2.x/en/project-admin/tools/pipelines/ |
CodeShiphttps://codeship.com |
|
|---|---|---|
| Unique feature |
DevOps tool for container orchestration
|
Runs on own infrastructure
|
| Type of product |
On Premise
|
SaaS
|
| Offers a free plan |
Yes Free, open source project |
Yes Free for up to 100 builds per month |
| Predictable pricing |
Yes It's free! |
Yes Clearly defined, calculator, expensive |
| Support / SLA |
Yes Paid support available: https://rancher.com/pricing/ |
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 You can run multiple parallel steps within a build stage |
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 Unclear from the documentation (probably not) |
No
|
| Containers support / Build environment |
Yes
|
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 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/ |
Yes
|
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes User management is available, with specific roles assigned, or permissions to certain resources and projects |
Yes Full with organization and teams management |
| Self-hosted option |
Yes
|
No
|
| Hosted plans / SaaS |
No
|
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 Pipelines as code (YML files), but also manageable via the UI |
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? |
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. |
N/A Pipelines / CI is just a small part of Rancher. No specific support mentioned. |
Yes Fairly complete documentation on Ruby projects: https://documentation.codeship.com/pro/languages-frameworks/ruby/ |
| Specific language support: JavaScript |
N/A Pipelines / CI is just a small part of Rancher. No specific support mentioned. |
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 Integrations available for GitLab, GitHub and Bitbucket |
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 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. |
Yes Custom integrations are possible: https://documentation.codeship.com/general/integrations/custom-integration/ |
| Auditing |
Yes Allows logging to various systems (Kafka, Elastic, etc) which should make audit possible |
N/A
|
| Additional notes |
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 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). |