Knapsack Pro
Knapsack Pro
AppVeyorhttps://www.appveyor.com |
Google Cloud Buildhttps://cloud.google.com/cloud-build/ |
|
|---|---|---|
| Unique feature |
Supports NuGet packages / Windows build environment
|
Security / speed
|
| Type of product |
SaaS / On Premise
|
SaaS
|
| Offers a free plan |
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) |
Yes Google offers a generous 120 build-minutes per day plan, not including time spent waiting in the queue. |
| Predictable pricing |
Yes Very simple pricing plans: 3 options for the SaaS version, two options for the on premise option. No variable pricing. |
Yes (partial) While it's clear what the cost is (priced per build-minute), figuring out costs can be a hassle, especially as the price can vary quite a bit depending on commits to the project. |
| Support / 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. |
Yes Even available as a paid add-on, for 24/7 phone support for example: https://cloud.google.com/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 Allows splitting tests to run on different VMs 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
|
N/A
|
| Containers support / Build environment |
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. |
Yes Native Docker and Packer 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 dashboard is not as great as for other options in the market, but allows seeing project status at a glance. |
Yes
|
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
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. |
Yes
|
| Self-hosted option |
Yes
|
No (partial) While there's no self hosted variant, they provide a local Cloud Build image which allows you to build locally, very valuable for debugging. |
| 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 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. |
Yes Configurable via YML and/or JSON files. |
|
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 Notifications are highly configurable, but visual reports such as code coverage is not easy to implement. |
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? |
N/A
|
Yes There are predefined images built for Cloud Build, which can be integrated right away in your build process. Some of them are first party: https://github.com/GoogleCloudPlatform/cloud-builders and others are community contributed: https://github.com/GoogleCloudPlatform/cloud-builders-community |
|
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 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. |
N/A Nothing specific as far as we can tell |
| Specific language support: JavaScript |
Yes Comes with node.js and io.js versions pre-installed. Also offers documentation on npm integration on their website. |
Yes (partial) npm, yarn and jasmine-node support via predefined Cloud Build steps. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
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). |
Yes Various integrations available via custom Build Steps, as well as natively (Kubernetes, Docker, etc.) |
|
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 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. |
Yes REST API and comprehensive CLI tool, as well as a pub/sub system for build notifications. |
| Auditing |
N/A
|
Yes
|
| Additional notes |
Very Windows oriented |
Not unlike other Google tools, there's a strong emphasis on allowing developers to build on top of the service. Becomes more valuable if you're using other Google Cloud services as well. |