e.g. 60 parallel nodes running 2 minutes each
e.g. 30 parallel nodes running 2 minutes each
e.g. 15 parallel nodes running 2 minutes each
Monthly you can save hours
and up to $
on faster development cycle.
I'd like to share with you my experience to optimise your CI pipeline. Please sign up and:
Founder of Knapsack Pro
We sum up the execution time of each of your test files. So, if your test suite has 1000 test files, each taking 1 second to run then it means your all test files take ~16,6 minutes. This fits Small plan up to 30 minutes test files limit.
The soft limits are applied to Knapsack Pro API usage so you can add more test suites for your new projects whenever you like.
We sum up the execution time of all your test files from all your API tokens (each set of tests you run with Knapsack Pro should have generated a unique API token in the Knapsack Pro user dashboard to track and run your test files properly).
Let's say your project has RSpec tests and you run CI build on a single machine for 40 minutes.
If you run the 40 minutes RSpec test suite with Knapsack Pro on 2 parallel nodes (node 0 takes 20 minutes and node 1 takes 20 minutes) then your project fits 1 hour test files plan because the total time of running RSpec test files is 20 minutes + 20 minutes = 40 minutes in total.
If you have additional tests like Cucumber and they took 50 minutes then your both test suites take 90 minutes in total (RSpec 40 minutes + Cucumber 50 minutes). Then your project fits up to 2 hours test files plan.
In other words, Knapsack Pro records total execution time of your test files from all your test suites (API tokens) executed across all parallel CI nodes. The total recorded time of your test files should fit up to the plan limit.
You can run as many parallel CI builds as you like. We count only test files execution time for pricing purposes.
You can use as many parallel CI nodes as your CI provider allows.
It's one of the parallel jobs (isolated server machine or Docker container) being part of the CI build. Knapsack Pro command is executed inside of each parallel job to run part of your whole test suite and thanks to that split all your tests across parallel machines. The configuration of parallel CI nodes depends on your current CI provider.
Knapsack Pro is CI provider agnostic. As long as you can define bash command per parallel job (parallel CI node) on your CI server then you can run Knapsack Pro with it. Knapsack Pro has built-in support for many popular CI providers.
There is no hard limit on the Knapsack Pro API side to cut you off if you exceed the test files time usage limit. Thanks to that you can test various CI configurations for your project or easily add Knapsack Pro to new projects.
If you happen to exceed limits or API usage would be much higher than for average customers then we will get in touch with you about a plan upgrade.
The price is based on the total execution time of all your test files from all your API tokens.
Feel free to try Knapsack Pro. We will contact you to better understand your project context and ensure the pricing is right for the value you get.
To qualify, your project needs just three things: