Knapsack Pro
Knapsack Pro
Netlify Buildhttps://www.netlify.com/products/build/ |
AppVeyorhttps://www.appveyor.com |
|
|---|---|---|
| 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. |
Supports NuGet packages / Windows build environment
|
| Type of product |
SaaS
|
SaaS / On Premise
|
| Offers a free plan |
Yes 300 build minutes/month, 1 concurrent CI build |
Yes Free SaaS plan for open source projects. There is also a free on premise version, but it's quite limited (1 user, 1 team, community support) |
| Predictable pricing |
Yes Extra 500 build minutes costs $7/month. User seat $15/user/month. |
Yes Very simple pricing plans: 3 options for the SaaS version, two options for the on premise option. No variable pricing. |
| Support / SLA |
Yes 99.99% uptime SLA for Starter and Pro plan. Business plan has negotiable SLA. |
Yes All paid on premise plans offer support, as well as the two higher priced SaaS plans. Only community support available for the free on premise version and the lowest SaaS tier. |
|
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 Allows splitting tests to run on different VMs 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 High-Performance Builds - The premium build environment gives more concurrency, processing power and asynchronous deploys. |
N/A
|
| 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 Runs every build in a VM, and it offers several options depending on the plan (SaaS or self-hosted) as well sa personal preference. |
|
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 The dashboard is not as great as for other options in the market, but allows seeing project status at a glance. |
|
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 Allows creating teams and assigning roles. There is some integration with GitHub Teams but the concepts are different which might be tricky depending on how the GitHub project is managed, for instance. |
| 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 There is a single predefined possible pipeline, which defines various hooks (such as before_build / after_build). The pipeline can be configured via the UI or via an appveyor.yml file. The two are mutually exclusive, so it's either one or the other. |
|
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 Notifications are highly configurable, but visual reports such as code coverage is not easy to implement. |
|
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. |
N/A
|
|
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 Many Ruby gems use AppVeyor as their CI server of choice. Among the features for Ruby are the pre-installed Ruby versions on both Windows and Ubuntu servers, as well as the appveyor-worker gem which makes it easy to report status during the build process. |
| Specific language support: JavaScript |
Yes It has support for JavaScript. |
Yes Comes with node.js and io.js versions pre-installed. Also offers documentation on npm integration on their website. |
|
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 Probably the most notable aspect here is the large array of deployment integrations available (from simple FTP uploads to Azure servers or NuGet packages). |
|
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 Offers a basic CRUD REST API for querying projects and builds as well as a real-time Build Worker API which can send updates on build status. |
| Auditing |
N/A
|
N/A
|
| Additional notes |
|
Very Windows oriented |