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 |
YesThe 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. |
YesFree, 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) |
YesIt's free! |
| Support / SLA |
YesCommunity 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. |
YesPaid 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 |
YesMatrix builds allow concurrent jobs, even multi-platform. |
YesYou 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/ANo specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available. |
N/AUnclear from the documentation (probably not) |
| Containers support / Build environment |
YesLinux, 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) |
YesMinimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes. |
YesNot 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/AUnclear from the available documentation |
YesUser management is available, with specific roles assigned, or permissions to certain resources and projects |
| Self-hosted option |
YesComing 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. |
YesCalled 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) |
YesPipelines 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/AUnclear 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? |
YesThanks 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. |
YesUnclear how, but they mention Ruby support specifically on the homepage |
N/APipelines / CI is just a small part of Rancher. No specific support mentioned. |
| Specific language support: JavaScript |
YesUnclear how, but they mention Javascript (Node.js) support specifically on the homepage |
N/APipelines / 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) |
YesIntegrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more) |
YesIntegrations 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/AUnclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available) |
YesREST 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 |
YesAllows 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. |
you have to wait 20 minutes for slow tests running too long on the red node
CI build completes work in only 10 minutes because Knapsack Pro ensures all parallel nodes finish work at a similar time
You can even run 20 parallel nodes to complete your CI build in 2 minutes
Step 1
Install Knapsack Pro client in your project
Step 2
Update your CI server config file to run tests in parallel with Knapsack Pro
Step 3
Run a CI build with parallel tests using Knapsack Pro
Knapsack Pro in Queue Mode splits tests in a dynamic way across parallel CI nodes to ensure each CI node finishes work at a similar time. Thanks to that, your CI build time is as fast as possible. It works with many supported CI servers.
| Programming Language | Supported test runners | Installation guide | Knapsack Pro Library README / Source |
|---|---|---|---|
| Ruby | RSpec, Cucumber, Minitest, test-unit, Spinach, Turnip | Install | knapsack_pro gem |
| JavaScript | Cypress.io | Install | @knapsack-pro/cypress |
| JavaScript | Jest | Install | @knapsack-pro/jest |
| JavaScript / TypeScript | Any test runner in JavaScript | How to build native integration with Knapsack Pro API to run tests in parallel for any test runner | @knapsack-pro/core |
| Any programming language | Any test runner | How to build a custom Knapsack Pro API client from scratch in any programming language | - |
Do you use other programming language or test runner? Let us know.
Run tests in parallel on Github Actions and Rancher Pipelines in the optimal way and avoid bottleneck parallel jobs.
Get started free
Monthly you can save hours
and up to $
on faster development cycle.
Dynamic tests allocation across Github Actions and Rancher Pipelines parallel jobs. Autobalance tests to get the optimal test suite split betweeen CI nodes.
Network issues? Not a problem, run tests anyway! Auto switch to the fallback mode to not depend on Knapsack Pro API.
Ruby: RSpec, Minitest, Test::Unit, Cucumber, Spinach, Turnip.
JavaScript: Cypress.io, Jest
API: Use native integration with Knapsack Pro API to run tests in parallel for any test runner
Other languages: How to build a custom Knapsack Pro API client from scratch in any programming language
Do you use different programming language or test runner? Let us know in the poll
Join the teams optimizing their tests with Knapsack Pro.
We've been really enjoying Knapsack Pro, it's been saving us a ton of time.
My team at @GustoHQ recently added @KnapsackPro to our CI. It's pretty sweet... It makes your builds faster _and_ (this is almost the better bit) more consistent! Thank you for the awesome tool!
— Stephan Hagemann (@shageman) September 26, 2022
This is a fantastic product, it's been a total game-changer for us.
We are using CircleCI and we noticed that builds were being limited by the slowest parallelized container. Knapsack Pro was really easy to setup and we saw huge improvements right away. Thank you for making this tool!
🛠How to run 7 hours of tests in 4 minutes using 100 parallel Buildkite agents and @KnapsackPro’s queue mode: https://t.co/zbXMIyNN8z
— Buildkite (@buildkite) March 29, 2017
Knapsack Pro has helped us build an insanely fast and scalable build pipeline with almost no setup or maintenance.
Knapsack Pro saves us hours of engineer waiting time every week, and is the best solution for keeping our tests load balanced that we've used to date.
I've been playing with Queue Mode. Love it! Wow, I love how fast it goes.
Awesome to see @NASA speeds up tests with #knapsack gem in https://t.co/GFOVW22dJn project! https://t.co/2GGbvnbQ7a #ruby #parallelisation
— KnapsackPro (@KnapsackPro) April 6, 2017
I just logged into my account expecting it to say that I needed to add a credit card and was so surprised and delighted to see the trial doesn't count usage by calendar days but by testing days! This is incredible! I love it!!!
I just wanted to say that I really appreciate that small but very huge feature. Thank you for being so thoughtful :)