Knapsack Pro

Github Actions vs Heroku CI comparison of Continuous Integration servers
What are the differences between Github Actions and Heroku CI?

Github Actions

https://github.com/features/actions

Heroku CI

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

Best GitHub integration possible

Heroku Flow

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.

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

Clearly defined, offers a calculator.

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

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

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

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

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

Yes

Great visual overview built-in.

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

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

Yes

Coming soon, not available yet.

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

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

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.

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

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.

Yes

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

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

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

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

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

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

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

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

N/A

Yes

Additional notes

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)

How to leverage Heroku CI to run your tests faster?

Introduction to Knapsack Pro Heroku add-on

Github Actions parallelism integration

Heroku CI parallelism integration

Start using Knapsack Pro with Github Actions or Heroku CI

Sign up and speed up your tests.

Get started free