Knapsack Pro
Knapsack Pro
CodeShiphttps://codeship.com |
Netlify Buildhttps://www.netlify.com/products/build/ |
|
|---|---|---|
| Unique feature |
Runs on own infrastructure
|
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. |
| Type of product |
SaaS
|
SaaS
|
| Offers a free plan |
Yes Free for up to 100 builds per month |
Yes 300 build minutes/month, 1 concurrent CI build |
| Predictable pricing |
Yes Clearly defined, calculator, expensive |
Yes Extra 500 build minutes costs $7/month. User seat $15/user/month. |
| Support / SLA |
Yes Offers great dev support |
Yes 99.99% uptime SLA for Starter and Pro plan. Business plan has negotiable SLA. |
|
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 Via easy Yaml config file, limited by the specs of the machine you have purchased |
Yes Starter plan (free) has only 1 concurrent build but Pro plan has 3 concurrent builds included. |
|
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 |
No
|
Yes High-Performance Builds - The premium build environment gives more concurrency, processing power and asynchronous deploys. |
| Containers support / Build environment |
Yes Native support for Docker |
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. |
|
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
|
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. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes Full with organization and teams management |
Yes Team members managment. Role-based access control only in business plan. |
| Self-hosted option |
No
|
No
|
| 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
|
Yes, partially Simple steps, define your own steps in bash commands |
|
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/A
|
No
|
|
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? |
N/A
|
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. |
|
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 Fairly complete documentation on Ruby projects: https://documentation.codeship.com/pro/languages-frameworks/ruby/ |
Yes It has support for Ruby. |
| Specific language support: JavaScript |
Yes Fairly complete documentation on Node.js projects: https://documentation.codeship.com/pro/languages-frameworks/nodejs/ |
Yes It has support for JavaScript. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Easy to integrate a bunch of 3rd party services, such as Code Climate, Codecov, Rancher, Pager Duty and many more: https://documentation.codeship.com/general/integrations/codeclimate/ |
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. |
|
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 Custom integrations are possible: https://documentation.codeship.com/general/integrations/custom-integration/ |
No
|
| Auditing |
N/A
|
N/A
|
| Additional notes |
CodeShip Pro gives you a lot more flexibility when defining your CI/CD process, plus you get your own AWS instance, so your build doesn't run on a shared server (this can be important for HIPAA or GDPR compliance, etc). |
|