Knapsack Pro

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

Buildkite

https://buildkite.com

Google Cloud Build

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

Runs on own infrastructure, API

Security / speed

Type of product

SaaS

SaaS

Offers a free plan

Yes

Free for open source projects and selected organizations

Yes

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

Predictable pricing

Yes

Clearly defined monthly and annual plans

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

Depending on the plan, ranging from community support, all the way to an assigned Technical Manager, SLAs and live chat 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

Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs. You can run your tests in isolated Docker container per agent.

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

Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs

N/A

Containers support / Build environment

Yes

Since the agents run on your own infra, you're free to do whatever

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

The Buildkite UI features great vizualisations that feature build times, error rates, and more.

Yes

Management support
How easy is it to manage users / projects / assign roles and permissions and so on

Yes

Yes

Self-hosted option

No

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

Pipelines are defined using an Yaml config file and allow for great flexibility in defining what each step of the process does.

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.

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

Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API). Growing number of community plugins: https://buildkite.com/plugins

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

You can find useful plugins like https://github.com/sj26/rspec-buildkite https://github.com/ticky/simplecov-buildkite etc

N/A

Nothing specific as far as we can tell

Specific language support: JavaScript

No

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 for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API)

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

Great GraphQL API, allows building your own dashboard with ease

Yes

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

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.

Buildkite parallel agents and how to use them for CI parallelisation

Buildkite parallelism integration

Start using Knapsack Pro with Buildkite or Google Cloud Build

Sign up and speed up your tests.

Get started free