Knapsack Pro
Knapsack Pro
Netlify Buildhttps://www.netlify.com/products/build/ |
Bitbucket Pipelineshttps://bitbucket.org/product/features/pipelines |
|
|---|---|---|
| Unique feature |
Deploy your sites to global Netlify infrastructure Every commit gets its own deployed version. Automatically attach a new Deploy Preview at a unique permanent URL whenever you submit a Pull/Merge Request. Set Netlify Build to deploy every branch in the repository for unlimited staging environments. |
Best Jira integration possible
|
| Type of product |
SaaS
|
SaaS / On Premise
|
| Offers a free plan |
Yes 300 build minutes/month, 1 concurrent CI build |
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 Extra 500 build minutes costs $7/month. User seat $15/user/month. |
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 99.99% uptime SLA for Starter and Pro plan. Business plan has negotiable SLA. |
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 Starter plan (free) has only 1 concurrent build but Pro plan has 3 concurrent builds included. |
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 |
Yes High-Performance Builds - The premium build environment gives more concurrency, processing power and asynchronous deploys. |
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 When you trigger a build on Netlify, their buildbot starts a Docker container to build your website. The buildbot will look for instructions about required languages and software needed to run your command before running build command. The instructions are called dependencies, and how you declare them depends on the programming languages and tools used in build. Build image selection is available. Until recently, all Netlify sites were built using the same build image. Netlify is experimenting with allowing customers to select from multiple Docker images with different operating systems and software versions. |
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 Simple dashboard to see CI builds. Other than CI analytics Netlify has Netlify Analytics that brings data captured directly from their servers for your website. |
Yes Excellent overview and contextual feedback. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes Team members managment. Role-based access control only in business plan. |
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, partially Simple steps, define your own steps in bash commands |
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. |
No
|
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? |
No There are only small helpful things like incoming webhooks so other services can trigger Netlify deploys, and send outgoing webhooks as a deploy starts, succeeds, or fails. |
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 It has support for Ruby. |
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 It has support for JavaScript. |
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 Netlify has incoming webhooks so other services can trigger Netlify deploys, and send outgoing webhooks as a deploy starts, succeeds, or fails. For instance you can integrate it with Slack. |
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 |
No
|
Yes
|
| Auditing |
N/A
|
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. |