Knapsack Pro
Knapsack Pro
GoCDhttps://www.gocd.org |
Netlify Buildhttps://www.netlify.com/products/build/ |
|
|---|---|---|
| Unique feature |
Free, open source CI/CD server
|
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 |
On Premise
|
SaaS
|
| Offers a free plan |
Yes Free, open source software. They provide some Enterprise add-ons and support at a cost though. |
Yes 300 build minutes/month, 1 concurrent CI build |
| Predictable pricing |
Yes For the Enterprise plans, they specify very clear tiers depending on the number of pipelines (directly correlated with the size of the organization) |
Yes Extra 500 build minutes costs $7/month. User seat $15/user/month. |
| Support / SLA |
Yes Paid support available for enterprise plans |
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
|
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 |
Yes They specify supporting tools like TLB (http://test-load-balancer.github.io/) which would require distributed builds. |
Yes High-Performance Builds - The premium build environment gives more concurrency, processing power and asynchronous deploys. |
| Containers support / Build environment |
Yes Native Docker and Kubernetes support |
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 One of the greatest things about GoCD is their Value Stream Map which allows tracing every pipeline through every stage, from code commit, to testing and deployment. They also offer various dashboards for seeing status at a glance. |
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 Allows managing users, assigning roles, and even defining user groups with specific rights for certain pipelines. |
Yes Team members managment. Role-based access control only in business plan. |
| Self-hosted option |
Yes
|
No
|
| Hosted plans / SaaS |
No
|
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 Fairly advanced support, from config files (YML, Groovy, JSON, etc) to API and UI interface for building and managing pipelines. |
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. |
Yes
|
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? |
Yes Wide array of plugins available: https://www.gocd.org/plugins/#artifact (although they seem to pride themselves on the fact that most common operations / needs are first class citizens, so no plugins needed) |
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 Available via plugins, such as the Gem repository poller: https://www.gocd.org/plugins/#package-repo |
Yes It has support for Ruby. |
| Specific language support: JavaScript |
Yes Available via plugins, such as the npm repository poller: https://www.gocd.org/plugins/#package-repo |
Yes It has support for JavaScript. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Integrations are also available via plugins (for notifications, LDAP authorization, Elastic agents and more): https://www.gocd.org/plugins/#notification |
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 You can build on top of GoCD in a variety of ways, from writing custom plugins to using the CCTray feed provided by it. |
No
|
| Auditing |
Yes
|
N/A
|
| Additional notes |
|
|