Knapsack Pro
Knapsack Pro
Gitlab CIhttps://about.gitlab.com/product/continuous-integration/ |
Rancher Pipelineshttps://rancher.com/docs/rancher/v2.x/en/project-admin/tools/pipelines/ |
|
|---|---|---|
| Unique feature |
AutoDev Ops / Allows keeping code management and CI in the same place
|
DevOps tool for container orchestration
|
| Type of product |
SaaS / On Premise
|
On Premise
|
| Offers a free plan |
Yes Very generous free plans for both the SaaS version as well as the on premise version. |
Yes Free, open source project |
| Predictable pricing |
Yes Clear and affordable pricing for both SaaS and self-hosted versions. |
Yes It's free! |
| Support / SLA |
Yes All paid plans include next business day 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 Easily configure jobs you want to be run in parallel via the YML config file (gitlab-ci.yml) |
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 |
Yes
|
N/A Unclear from the documentation (probably not) |
| Containers support / Build environment |
Yes The Docker Container Registry is integrated into GitLab by default |
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
|
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 Defined via YML config files |
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
|
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 Although not built into GitLab CI by default, the Docker support allows solving any Ruby specific need that may arise. |
N/A Pipelines / CI is just a small part of Rancher. No specific support mentioned. |
| Specific language support: JavaScript |
Yes Although not built into GitLab CI by default, the Docker support allows solving any Javascript specific need that may arise. |
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 Plenty of third party integrations available throughout GitLab, most notably Kubernetes and GitHub, but also plenty of others: https://docs.gitlab.com/ee/integration/README.html |
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 REST API and a (new) GraphQL API, with plans to maintain the GraphQL API only going forward. Allows doing almost anything that can be done via the interface, at least in terms of CI needs. |
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 |
The Auto DevOps feature might be interesting to people looking for a very hands-off experience with getting a CI/CD process up and running https://docs.gitlab.com/ee/topics/autodevops/ |
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. |