Github Actions vs Heroku CI

Overview

Heroku CI

Stacks90

Followers132

Votes5

GitHub Actions

Stacks48.2K

Followers3.1K

Votes27

Github Actions vs Heroku CI: What are the differences?

Integration with platform: GitHub Actions is tightly integrated with GitHub repositories, allowing seamless automation of workflows within the same ecosystem. On the other hand, Heroku CI is specifically designed for continuous integration and deployment on the Heroku platform, providing native support for deploying applications to Heroku.
Pricing: GitHub Actions offers a generous free tier for public repositories and limited usage on private repositories, with additional costs based on usage beyond the limits. In comparison, Heroku CI is an addon service provided by Heroku, with pricing based on the number of test runs and parallel test instances required.
Scalability: GitHub Actions provides scalable workflows that can be easily customized and managed for projects of any size, with the ability to run parallel jobs concurrently. Heroku CI, being a platform-specific tool, is more limited in scalability compared to GitHub Actions.
Customizability: GitHub Actions allows for extensive customization using YAML-based configuration files, offering flexibility in defining workflows, triggers, and actions. Heroku CI, while providing some customization options, may be more restrictive in terms of configuration compared to GitHub Actions.
Environment support: GitHub Actions supports a wide range of operating systems, programming languages, and tools, allowing developers to build and test applications in diverse environments. In contrast, Heroku CI is primarily focused on supporting applications deployed on the Heroku platform, which may limit the scope of environments that can be tested.
Deployment capabilities: While both GitHub Actions and Heroku CI enable continuous integration and deployment workflows, GitHub Actions can be used to deploy applications to various platforms beyond just Heroku, providing more flexibility in deployment options compared to Heroku CI.

In Summary, GitHub Actions and Heroku CI differ in terms of platform integration, pricing, scalability, customizability, environment support, and deployment capabilities.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Heroku CI, GitHub Actions

Somnath

Engineering Leader at Altimetrik Corp.

Jun 25, 2020

Needs adviceon

CircleCI

Drone.io

GitHub Actions

I am in the process of evaluating CircleCI, Drone.io, and GitHub Actions to cover my #CI/ #CD needs. I would appreciate your advice on comparative study w.r.t. attributes like language-Inclusive support, code-base integration, performance, cost, maintenance, support, ease of use, ability to deal with big projects, etc. based on actual industry experience.

Thanks in advance!

1.82M views1.82M

Comments

Detailed Comparison

Heroku CI	GitHub Actions
On every push to GitHub, Heroku CI runs your tests in a disposable Heroku app, so there’s never a wait time for a free CI worker. Tests run fast, on Performance dynos.	It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
-	Multiple workflow files support; Free and open source; Workflow run interface; Search for actions in GitHub Marketplace; Integrated with Github's Checks API; Logs and artifacts downloading support
Statistics
Stacks 90	Stacks 48.2K
Followers 132	Followers 3.1K
Votes 5	Votes 27
Pros & Cons
Pros 3 No waiting in the queue 1 Best in class pipeline integration 1 Consolidated Heroku billing	Pros 8 Integration with GitHub 5 Free 3 Ready actions in Marketplace 3 Easy to duplicate a workflow 2 Read actions in Marketplace Cons 5 Lacking [skip ci] 4 Lacking allow failure 3 Lacking job specific badges 2 No ssh login to servers 1 No manual launch
Integrations
Heroku GitHub	GitHub

What are some alternatives to Heroku CI, GitHub Actions?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Airflow

Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command lines utilities makes performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress and troubleshoot issues when needed.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Related Comparisons

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

Github Actions vs Heroku CI: What are the differences?

Integration with platform: GitHub Actions is tightly integrated with GitHub repositories, allowing seamless automation of workflows within the same ecosystem. On the other hand, Heroku CI is specifically designed for continuous integration and deployment on the Heroku platform, providing native support for deploying applications to Heroku.
Pricing: GitHub Actions offers a generous free tier for public repositories and limited usage on private repositories, with additional costs based on usage beyond the limits. In comparison, Heroku CI is an addon service provided by Heroku, with pricing based on the number of test runs and parallel test instances required.
Scalability: GitHub Actions provides scalable workflows that can be easily customized and managed for projects of any size, with the ability to run parallel jobs concurrently. Heroku CI, being a platform-specific tool, is more limited in scalability compared to GitHub Actions.
Customizability: GitHub Actions allows for extensive customization using YAML-based configuration files, offering flexibility in defining workflows, triggers, and actions. Heroku CI, while providing some customization options, may be more restrictive in terms of configuration compared to GitHub Actions.
Environment support: GitHub Actions supports a wide range of operating systems, programming languages, and tools, allowing developers to build and test applications in diverse environments. In contrast, Heroku CI is primarily focused on supporting applications deployed on the Heroku platform, which may limit the scope of environments that can be tested.
Deployment capabilities: While both GitHub Actions and Heroku CI enable continuous integration and deployment workflows, GitHub Actions can be used to deploy applications to various platforms beyond just Heroku, providing more flexibility in deployment options compared to Heroku CI.

In Summary, GitHub Actions and Heroku CI differ in terms of platform integration, pricing, scalability, customizability, environment support, and deployment capabilities.