Knapsack Pro
Knapsack Pro
Shippablehttps://www.shippable.com |
Bitbucket Pipelineshttps://bitbucket.org/product/features/pipelines |
|
|---|---|---|
| Unique feature |
N/A
|
Best Jira integration possible
|
| Type of product |
SaaS / On Premise
|
SaaS / On Premise
|
| Offers a free plan |
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. |
Yes Offers a very modest free cloud plan, limited to 5 users, 50 minutes of build time per month and 1GB storage. There's no free self-hosted version, but they do offer a $10 one-time payment plan for 10 users (build time and storage is only limited by your infrastructure) |
| Predictable pricing |
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) |
Yes Pricing is based on amount of users for both the cloud and on premise versions. The cloud offering has different tiers depending on build times and storage. |
| Support / SLA |
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 |
Yes Dedicated tehnical support. |
|
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 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 |
Yes
|
|
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. 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. |
N/A Documentation is unclear, but it's reasonable to assume that distributed builds for the on premise version are not an issue. |
| Containers support / Build environment |
Yes Native Docker support |
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 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. |
Yes Excellent overview and contextual feedback. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes
|
Yes
|
| Self-hosted option |
Yes
|
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 Configurable via an YML file (called Assembly Lines) |
Yes
|
|
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 https://www.shippable.com/integrations.html |
Yes Large collection of available apps: https://confluence.atlassian.com/bitbucket/apps-and-integrations-675189068.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 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/ |
Yes Clear, concise documentation on setting up a Ruby project with Bitbucket pipelines: https://confluence.atlassian.com/bitbucket/ruby-with-bitbucket-pipelines-872005618.html |
| Specific language support: JavaScript |
Yes Specific documentation for Node.js available: http://docs.shippable.com/ci/ruby-continuous-integration/ |
Yes Clear, concise documentation on setting up a Javascript project with Bitbucket pipelines: https://confluence.atlassian.com/bitbucket/javascript-node-js-with-bitbucket-pipelines-873891287.html |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes http://docs.shippable.com/ci/ruby-continuous-integration/ |
Yes Large collection of available integrations: https://confluence.atlassian.com/bitbucket/apps-and-integrations-675189068.html |
|
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 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/ |
Yes
|
| Auditing |
Yes
|
Yes
|
| Additional notes |
|
There's some confusion regarding Bitbucket Pipelines and Bamboo, where they overlap and where not. Atlassian discontinued their Bamboo Cloud offering ~3 years ago, so at a high-level they are different products in that regard. What can be said about both is that they are top-tier tools for high-demand engineering teams, especially valuable as long as the other tools in the Atlassian suite are adopted (Bitbucket is a must for Bitbucket pipelines, being just one if it's features, but other tools like Jira are not to be dismissed either). It does seem like Bitbucket Pipelines is the more mature product of the two though. |