Shippablehttps://www.shippable.com |
Rancher Pipelineshttps://rancher.com/docs/rancher/v2.x/en/project-admin/tools/pipelines/ |
|
---|---|---|
Unique feature |
N/A
|
DevOps tool for container orchestration
|
Type of product |
SaaS / On Premise
|
On Premise
|
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, open source project |
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 It's free! |
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 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 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 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 |
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. |
N/A Unclear from the documentation (probably not) |
Containers support / Build environment |
Yes Native Docker support |
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 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 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
|
Yes User management is available, with specific roles assigned, or permissions to certain resources and projects |
Self-hosted option |
Yes
|
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 Configurable via an YML file (called Assembly Lines) |
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. |
Yes
|
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? |
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/ |
N/A Pipelines / CI is just a small part of Rancher. No specific support mentioned. |
Specific language support: JavaScript |
Yes Specific documentation for Node.js available: http://docs.shippable.com/ci/ruby-continuous-integration/ |
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 http://docs.shippable.com/ci/ruby-continuous-integration/ |
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 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 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 |
Yes
|
Yes Allows logging to various systems (Kafka, Elastic, etc) which should make audit possible |
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. |