Knapsack Pro
Knapsack Pro
Buildkitehttps://buildkite.com |
Shippablehttps://www.shippable.com |
|
|---|---|---|
| Unique feature |
Runs on own infrastructure, API
|
N/A
|
| Type of product |
SaaS
|
SaaS / On Premise
|
| Offers a free plan |
Yes Free for open source projects and selected organizations |
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. |
| Predictable pricing |
Yes Clearly defined monthly and annual plans |
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) |
| Support / SLA |
Yes Depending on the plan, ranging from community support, all the way to an assigned Technical Manager, SLAs and live chat support. |
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 |
|
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 Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs. You can run your tests in isolated Docker container per agent. |
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 |
|
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 Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs |
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. |
| Containers support / Build environment |
Yes Since the agents run on your own infra, you're free to do whatever |
Yes Native Docker support |
|
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 The Buildkite UI features great vizualisations that feature build times, error rates, and more. |
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. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes
|
Yes
|
| Self-hosted option |
No
|
Yes
|
| Hosted plans / SaaS |
Yes
|
Yes
|
|
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 Pipelines are defined using an Yaml config file and allow for great flexibility in defining what each step of the process does. |
Yes Configurable via an YML file (called Assembly Lines) |
|
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 Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API). Growing number of community plugins: https://buildkite.com/plugins |
Yes https://www.shippable.com/integrations.html |
|
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 You can find useful plugins like https://github.com/sj26/rspec-buildkite https://github.com/ticky/simplecov-buildkite etc |
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/ |
| Specific language support: JavaScript |
No
|
Yes Specific documentation for Node.js available: http://docs.shippable.com/ci/ruby-continuous-integration/ |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API) |
Yes http://docs.shippable.com/ci/ruby-continuous-integration/ |
|
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 Great GraphQL API, allows building your own dashboard with ease |
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/ |
| Auditing |
Yes
|
Yes
|
| Additional notes |
|
|