Knapsack Pro
Knapsack Pro
GoCDhttps://www.gocd.org |
Dronehttps://drone.io |
|
|---|---|---|
| Unique feature |
Free, open source CI/CD server
|
Customization
|
| Type of product |
On Premise
|
SaaS / On Premise
|
| Offers a free plan |
Yes Free, open source software. They provide some Enterprise add-ons and support at a cost though. |
Yes The cloud version is free for open source projects. Also offers a free plan for any project, with a limit of 5000 builds per year. The on-premise version is available as a Docker image. |
| 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 Predictable pricing based on number of users and repositories. They have a calculator to help determine cost. |
| Support / SLA |
Yes Paid support available for enterprise plans |
N/A It's not clear what their support commitment is. They have a fairly active community on Discourse, for community 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
|
Yes Pipeline task configuration allows running tasks 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 They specify supporting tools like TLB (http://test-load-balancer.github.io/) which would require distributed builds. |
Yes Pipelines can be configured to run on multiple machines, although they recommend that to be an option only if paralellizing tasks and scaling vertically doesn't suffice. They even support multi-platform distribution (ie: running tasks on various operating systems) |
| Containers support / Build environment |
Yes Native Docker and Kubernetes support |
Yes By default, they offer Docker support for the CI/CD job runners. |
|
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
|
|
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 They offer in-depth documentation for user and server management. A lot of it can be done via the drone CLI tool, which seems to be the focal point of the docs. |
| Self-hosted option |
Yes
|
Yes
|
| 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 Easily configurable pipelines via YML 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
|
N/A
|
|
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) |
Yes Drone CI allows integrating plugins into the CI/CD process. They have a list of available community plugins and provide documentation on building your own. Plugins are Docker containers which plug directly into the CI/CD process. |
|
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 |
No (partial) No specific support, but they do provide sufficient documentation on getting a Ruby project up and running, including a multi-platform example. |
| Specific language support: JavaScript |
Yes Available via plugins, such as the npm repository poller: https://www.gocd.org/plugins/#package-repo |
No (partial) No specific 1st party support, but the plugin marketplace features an NPM authoring and an NPM authentication plugin. |
|
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 Integrates well with source code management platforms (1st party support for GitHub, GitLab, BitBucket) as well as other systems via 3rd party plugins. |
|
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. |
Yes Drone provides a feature-rich REST API, as well as an official Go SDK for it. |
| Auditing |
Yes
|
Yes
|
| Additional notes |
|
The fact that Drone works with any source code manager, as well as the fact that it can run tasks on multiple platforms makes it stand out from the rest. Very nifty! |