Knapsack Pro
Knapsack Pro
Gitlab CIhttps://about.gitlab.com/product/continuous-integration/ |
GoCDhttps://www.gocd.org |
|
|---|---|---|
| Unique feature |
AutoDev Ops / Allows keeping code management and CI in the same place
|
Free, open source CI/CD server
|
| Type of product |
SaaS / On Premise
|
On Premise
|
| Offers a free plan |
Yes Very generous free plans for both the SaaS version as well as the on premise version. |
Yes Free, open source software. They provide some Enterprise add-ons and support at a cost though. |
| Predictable pricing |
Yes Clear and affordable pricing for both SaaS and self-hosted versions. |
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 All paid plans include next business day 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 Easily configure jobs you want to be run in parallel via the YML config file (gitlab-ci.yml) |
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 |
Yes
|
Yes They specify supporting tools like TLB (http://test-load-balancer.github.io/) which would require distributed builds. |
| Containers support / Build environment |
Yes The Docker Container Registry is integrated into GitLab by default |
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
|
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 |
Yes
|
Yes Allows managing users, assigning roles, and even defining user groups with specific rights for certain pipelines. |
| Self-hosted option |
Yes
|
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 Defined via YML config files |
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. |
Yes
|
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
|
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 Although not built into GitLab CI by default, the Docker support allows solving any Ruby specific need that may arise. |
Yes Available via plugins, such as the Gem repository poller: https://www.gocd.org/plugins/#package-repo |
| Specific language support: JavaScript |
Yes Although not built into GitLab CI by default, the Docker support allows solving any Javascript specific need that may arise. |
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 Plenty of third party integrations available throughout GitLab, most notably Kubernetes and GitHub, but also plenty of others: https://docs.gitlab.com/ee/integration/README.html |
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 |
Yes Provides a REST API and a (new) GraphQL API, with plans to maintain the GraphQL API only going forward. Allows doing almost anything that can be done via the interface, at least in terms of CI needs. |
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 |
Yes
|
Yes
|
| Additional notes |
The Auto DevOps feature might be interesting to people looking for a very hands-off experience with getting a CI/CD process up and running https://docs.gitlab.com/ee/topics/autodevops/ |
|