Knapsack Pro
Knapsack Pro
Google Cloud Buildhttps://cloud.google.com/cloud-build/ |
Gitlab CIhttps://about.gitlab.com/product/continuous-integration/ |
|
|---|---|---|
| Unique feature |
Security / speed
|
AutoDev Ops / Allows keeping code management and CI in the same place
|
| Type of product |
SaaS
|
SaaS / On Premise
|
| Offers a free plan |
Yes Google offers a generous 120 build-minutes per day plan, not including time spent waiting in the queue. |
Yes Very generous free plans for both the SaaS version as well as the on premise version. |
| 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. |
Yes Clear and affordable pricing for both SaaS and self-hosted versions. |
| Support / SLA |
Yes Even available as a paid add-on, for 24/7 phone support for example: https://cloud.google.com/support/ |
Yes All paid plans include next business day 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 Easily configure jobs you want to be run in parallel via the YML config file (gitlab-ci.yml) |
|
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
|
Yes
|
| Containers support / Build environment |
Yes Native Docker and Packer support |
Yes The Docker Container Registry is integrated into GitLab by default |
|
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
|
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes
|
Yes
|
| Self-hosted option |
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. |
Yes
|
| 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 Configurable via YML and/or JSON files. |
Yes Defined via YML config 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
|
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 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 |
Yes
|
|
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. |
N/A Nothing specific as far as we can tell |
Yes Although not built into GitLab CI by default, the Docker support allows solving any Ruby specific need that may arise. |
| Specific language support: JavaScript |
Yes (partial) npm, yarn and jasmine-node support via predefined Cloud Build steps. |
Yes Although not built into GitLab CI by default, the Docker support allows solving any Javascript specific need that may arise. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Various integrations available via custom Build Steps, as well as natively (Kubernetes, Docker, 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 |
|
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 REST API and comprehensive CLI tool, as well as a pub/sub system for build notifications. |
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. |
| Auditing |
Yes
|
Yes
|
| Additional notes |
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. |
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/ |