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

Google Cloud Build

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

Heroku CI

https://www.heroku.com/continuous-integration
Unique feature

Security / speed

Heroku Flow

Type of product

SaaS

SaaS

Offers a free plan

Yes

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

No (partial)

For CI only, the cost starts at $10 for pipeline, plus a variable amount depending on how long the build runs for (prorated per second). The servers used for CI cost $250 for a full month, which means you get about 3 hours for $1. For hosting, there's a free tier, limited to 1 web/1 worker with 512 MB RAM. One of the more annoying limitations is that free dynos are put into sleep mode after 30 min. of inactivity, which increases loading times considerably.
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

Clearly defined, offers a calculator.
Support / SLA

Yes

Even available as a paid add-on, for 24/7 phone support for example: https://cloud.google.com/support/

Yes

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 optimal way with Knapsack Pro

Yes

Yes

Up to 16 nodes. You can ask Heroku support to enable up to 32 parallel dynos.
Distributed builds
distributed means that tasks can be scaled horizontally, on multiple machines
How to split tests in parallel in optimal way with Knapsack Pro

N/A

N/A

Containers support / Build environment

Yes

Native Docker and Packer support

Yes

Builds run in isolation on new dynos (Heroku containers). Wide support via buildpacks: https://devcenter.heroku.com/articles/buildpacks
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

Great visual overview built-in.
Management support
How easy is it to manage users / projects / assign roles and permissions and so on

Yes

Yes

One of the more mature solutions for teams on the market, Heroku Teams is available for free for 1-5 people, and comes at a cost for 6+ team members: https://www.heroku.com/pricing#team-comparison. Allows setting roles and app-level permissions with ease.
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.

No

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

Very easy and intuitive process that allows defining a pipeline from code commit, to code review (review apps), user acceptance testing and production deployment, via Heroku Flow. Works best if the project is also hosted on Heroku.
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

Wide array of 3rd party add-ons available via Heroku Elements: https://elements.heroku.com/addons. Custom buildpacks are also available for almost any stack you might be using (over 5500 buildpacks available at the moment)
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 specifically built in to Heroku, it's guaranteed that any Ruby specific need that might arise would be solved via add-ons, buildpacks or other integrations available.
Specific language support: JavaScript

Yes (partial)

npm, yarn and jasmine-node support via predefined Cloud Build steps.

Yes

Although not specifically built in to Heroku, it's guaranteed that any Javascript specific need that might arise would be solved via add-ons, buildpacks or other integrations available.
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

The strongest built-in integrations are with GitHub and Slack (ChatOps) but even allows integrating 3rd party CI servers in the workflow if you so require, among others.
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

Offers a feature rich API that allows CRUD operations on the most important features, such as promoting an app to production, or inspecting a specific pipeline.
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.

How to run parallel tests on Google Cloud Build and Heroku CI
to execute 1-hour test suite in 2 minutes?

How it works

1. Install Knapsack Pro client in your project


2. Add Knapsack Pro client to your current CI server and run your tests in parallel



3. Update your CI server config file to run tests in parallel with Knapsack Pro

Knapsack Pro in Queue Mode will split tests in a dynamic way across parallel CI nodes to ensure each CI node finish work at a similar time. Thanks to that your CI build time is as fast as possible. It works with many supported CI servers.

Do you know

Start using Knapsack Pro

Sign up and speed up your tests.

Get faster feedback from Google Cloud Build and Heroku CI server

  • save time & money
  • deliver features faster
  • catch errors earlier

How to leverage Heroku CI to run your tests faster?

Introduction to Knapsack Pro Heroku add-on

Heroku CI parallelism integration

Introduction to CI parallelisation with Knapsack Pro

Run tests in parallel on Google Cloud Build and Heroku CI in optimal way and avoid bottleneck parallel jobs.

How much can you save with faster tests
on Google Cloud Build and Heroku CI?

minutes
$

Monthly you can save hours
and up to $
on faster development cycle.

Features that make your tests perform better

  • Queue mode see video

    Dynamic tests allocation across Google Cloud Build and Heroku CI parallel jobs. Autobalance tests to get optimal test suite split betweeen CI nodes.

  • Regular mode see video

    Test suite split based on time execution. Generates subset of test suite per CI node before running tests.

  • Fallback mode

    Network issues? Not a problem, run tests anyway! Auto switch to the fallback mode to not depend on Knapsack Pro API.

  • All supported test runners

    Ruby: RSpec, Minitest, Test::Unit, Cucumber, Spinach, Turnip.

    JavaScript: Cypress.io, Jest

    Do you use different programming language or test runner? Let us know in the poll

Discover all features or see
how to use Knapsack Pro with your CI

Trusted solution

Join the teams optimizing their tests with Knapsack Pro.

We've been really enjoying Knapsack Pro, it's been saving us a ton of time.

Devin Brown Software Engineer at Pivotal

This is a fantastic product, it's been a total game-changer for us.

Geoff Harcourt CTO at CommonLit

We are using CircleCI and we noticed that builds were being limited by the slowest parallelized container. Knapsack Pro was really east to setup and we saw huge improvements right away. Thank you for making this tool!

Martin Sieniawski Software Engineer at Collage

Knapsack Pro has helped us build an insanely fast and scaleable build pipeline with almost no setup or maintenance.

Tim Lucas Co-founder of buildkite.com

Knapsack Pro saves us hours of engineer waiting time every week, and is the best solution for keeping our tests load balanced that we've used to date.

Michael Amygdalidis Senior Software Engineer at Popular Pays

I've been playing with Queue Mode. Love it! Wow, I love how fast it goes.

Michael Menne CTO at humanagency.org

I just logged into my account expecting it to say that I needed to add a credit card and was so surprised and delighted to see the trial doesn't count usage by calendar days but by testing days! This is incredible! I love it!!!

I just wanted to say that I really appreciate that small but very huge feature. Thank you for being so thoughtful :)

Shannon Baffoni Senior Software Engineer
at Blue Bottle Coffee

See more testimonials

Start using Knapsack Pro with Google Cloud Build or Heroku CI

Sign up and speed up your tests.