Knapsack Pro
Knapsack Pro
Cirrus CIhttps://cirrus-ci.org |
Google Cloud Buildhttps://cloud.google.com/cloud-build/ |
|
|---|---|---|
| Unique feature |
FreeBSD support
|
Security / speed
|
| Type of product |
SaaS / On Premise
|
SaaS
|
| Offers a free plan |
Yes Free for open source projects |
Yes Google offers a generous 120 build-minutes per day plan, not including time spent waiting in the queue. |
| Predictable pricing |
Yes Besides the seat (per-user access) you need to buy compute credits for running the build, priced differently depending on the machine you're running builds on. |
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. |
| Support / SLA |
N/A Not clear if they offer any real SLA on support. |
Yes Even available as a paid add-on, for 24/7 phone support for example: https://cloud.google.com/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 There are limits on how many tasks can be run in parallel for the free tier builds: https://cirrus-ci.org/faq/#are-there-any-limits |
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
|
N/A
|
| Containers support / Build environment |
Yes Allows containers or VMs for every major operating system. |
Yes Native Docker and Packer 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
|
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
N/A
|
Yes
|
| Self-hosted option |
Yes
|
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. |
| 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 Defined via YML config files |
Yes Configurable via YML and/or JSON 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. |
N/A
|
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? |
N/A
|
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 |
|
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. |
No (partial) No specific support from what I can gather, but it does provide documentation for Ruby, including integration with the knapsack_pro gem. |
N/A Nothing specific as far as we can tell |
| Specific language support: JavaScript |
No No specific support and no documentation on setting up a CI/CD process for a Javascript project. |
Yes (partial) npm, yarn and jasmine-node support via predefined Cloud Build steps. |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Integrates well with GitHub - the whole CI/CD process starts with a commit to a GitHub repo. |
Yes Various integrations available via custom Build Steps, as well as natively (Kubernetes, Docker, etc.) |
|
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 pretty nifty GraphQL API which allows querying the Cirrus CI Schema, as well as webhooks support for other types of custom integrations (such as Slack or IRC notifications, for example). They also added support for GitHub actions |
Yes REST API and comprehensive CLI tool, as well as a pub/sub system for build notifications. |
| Auditing |
N/A From what we can tell, there's no specific support for auditing changes in the Cirrus CI config (other than what is traceable via git commits to the YML config file) |
Yes
|
| Additional notes |
Seems to be used by companies with a solid engineering background (Google) |
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. |