Knapsack Pro
Knapsack Pro
Github Actionshttps://github.com/features/actions |
Rancher Pipelineshttps://rancher.com/docs/rancher/v2.x/en/project-admin/tools/pipelines/ |
|
|---|---|---|
| Unique feature |
Best GitHub integration possible
|
DevOps tool for container orchestration
|
| Type of product |
SaaS / On Premise
|
On Premise
|
| Offers a free plan |
Yes The on premise plan (not yet available) will be free, 2000 build minutes included in the free cloud plan. Completely free plan for open source projects. |
Yes Free, open source project |
| Predictable pricing |
Yes (partial) While it's clear what the cost is (priced per build-minute), figuring out costs can be a hassle, especially as the price can vary quite a bit depending on commits to the project. One advantage for GitHub Actions is that the tiers define a maximum amount of minutes, so it's easier to predict the final cost. You can also purchase aditional runners with pricing dependent on the platform (MacOS, Linux, Windows) |
Yes It's free! |
| Support / SLA |
Yes Community support available for any tier, unclear at what point and if dedicated support is available. Safe to assume that eneterprise clients can access technical 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 Matrix builds allow concurrent jobs, even multi-platform. |
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, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available. |
N/A Unclear from the documentation (probably not) |
| Containers support / Build environment |
Yes Linux, macOS, Windows, and containers, or run directly in a VM. |
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 Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes. |
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 |
N/A Unclear from the available documentation |
Yes User management is available, with specific roles assigned, or permissions to certain resources and projects |
| Self-hosted option |
Yes Coming soon, not available yet. |
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 Called GitHub Action Workflows, they are defined in separate Docker containers, using the YAML syntax (they used to support HCL, but they're migrating away from that) |
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. |
N/A Unclear from the available documentation |
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 Thanks to the large following, GitHub Actions already enjoys a wide varierty of available pre-made workflows, which you can browse right on the homepage: https://github.com/features/actions |
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 Unclear how, but they mention Ruby support specifically on the homepage |
N/A Pipelines / CI is just a small part of Rancher. No specific support mentioned. |
| Specific language support: JavaScript |
Yes Unclear how, but they mention Javascript (Node.js) support specifically on the homepage |
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 Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more) |
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 |
N/A Unclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available) |
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 |
N/A
|
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. |