Knapsack Pro
Knapsack Pro
Github Actionshttps://github.com/features/actions |
GoCDhttps://www.gocd.org |
|
|---|---|---|
| Unique feature |
Best GitHub integration possible
|
Free, open source CI/CD server
|
| Type of product |
SaaS / On Premise
|
On Premise
|
| Offers a free plan |
Yes The on premise plan (not yet available) will be free, 2000 build minutes included in the free cloud plan. Completely free plan for open source projects. |
Yes Free, open source software. They provide some Enterprise add-ons and support at a cost though. |
| Predictable 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. One advantage for GitHub Actions is that the tiers define a maximum amount of minutes, so it's easier to predict the final cost. You can also purchase aditional runners with pricing dependent on the platform (MacOS, Linux, Windows) |
Yes For the Enterprise plans, they specify very clear tiers depending on the number of pipelines (directly correlated with the size of the organization) |
| Support / SLA |
Yes Community support available for any tier, unclear at what point and if dedicated support is available. Safe to assume that eneterprise clients can access technical support. |
Yes Paid support available for enterprise plans |
|
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 Matrix builds allow concurrent jobs, even multi-platform. |
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 No specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available. |
Yes They specify supporting tools like TLB (http://test-load-balancer.github.io/) which would require distributed builds. |
| Containers support / Build environment |
Yes Linux, macOS, Windows, and containers, or run directly in a VM. |
Yes Native Docker and Kubernetes 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 Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes. |
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. |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
N/A Unclear from the available documentation |
Yes Allows managing users, assigning roles, and even defining user groups with specific rights for certain pipelines. |
| Self-hosted option |
Yes Coming soon, not available yet. |
Yes
|
| Hosted plans / SaaS |
Yes
|
No
|
|
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 Called GitHub Action Workflows, they are defined in separate Docker containers, using the YAML syntax (they used to support HCL, but they're migrating away from that) |
Yes Fairly advanced support, from config files (YML, Groovy, JSON, etc) to API and UI interface for building and managing pipelines. |
|
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 Unclear from the available documentation |
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? |
Yes Thanks to the large following, GitHub Actions already enjoys a wide varierty of available pre-made workflows, which you can browse right on the homepage: https://github.com/features/actions |
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) |
|
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 Unclear how, but they mention Ruby support specifically on the homepage |
Yes Available via plugins, such as the Gem repository poller: https://www.gocd.org/plugins/#package-repo |
| Specific language support: JavaScript |
Yes Unclear how, but they mention Javascript (Node.js) support specifically on the homepage |
Yes Available via plugins, such as the npm repository poller: https://www.gocd.org/plugins/#package-repo |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more) |
Yes Integrations are also available via plugins (for notifications, LDAP authorization, Elastic agents and more): https://www.gocd.org/plugins/#notification |
|
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 |
N/A Unclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available) |
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. |
| Auditing |
N/A
|
Yes
|
| Additional notes |
|
|