Knapsack Pro

Github Actions vs Google Cloud Build comparison of Continuous Integration servers
What are the differences between Github Actions and Google Cloud Build?

Github Actions

https://github.com/features/actions

Google Cloud Build

https://cloud.google.com/cloud-build/
Unique feature

Best GitHub integration possible

Security / speed

Type of product

SaaS / On Premise

SaaS

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

Google offers a generous 120 build-minutes per day plan, not including time spent waiting in the queue.

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 (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

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

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

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.

N/A

Containers support / Build environment

Yes

Linux, macOS, Windows, and containers, or run directly in a VM.

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

Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes.

Yes

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

Self-hosted option

Yes

Coming soon, not available yet.

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

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

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

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

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.

Yes

Unclear how, but they mention Ruby support specifically on the homepage

N/A

Nothing specific as far as we can tell

Specific language support: JavaScript

Yes

Unclear how, but they mention Javascript (Node.js) support specifically on the homepage

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

Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more)

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

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

REST API and comprehensive CLI tool, as well as a pub/sub system for build notifications.

Auditing

N/A

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.

GitHub Actions testing Ruby on Rails with RSpec and parallel jobs (matrix feature)

How to run Jest tests on GitHub Actions - JS parallel jobs with matrix feature (NodeJS YAML config)

GitHub Actions Cypress.io E2E testing parallel jobs with matrix feature (NodeJS YAML config)

Github Actions parallelism integration

Start using Knapsack Pro with Github Actions or Google Cloud Build

Sign up and speed up your tests.

Get started free