CircleCI vs Heroku CI

Overview

CircleCI

Stacks14.5K

Followers7.1K

Votes974

Heroku CI

Stacks90

Followers132

Votes5

CircleCI vs Heroku CI: What are the differences?

Hosting Platform: CircleCI is primarily a continuous integration and delivery platform, while Heroku CI is a continuous integration service provided by Heroku, a platform as a service (PaaS) provider. CircleCI is focused on automating the build, test, and deploy processes, while Heroku CI is an extension of the Heroku platform that allows for continuous integration.
Integration with Other Services: CircleCI integrates seamlessly with popular version control systems like GitHub and Bitbucket, as well as other services such as Slack for notifications. On the other hand, Heroku CI is tightly integrated with the Heroku platform, streamlining the process of deploying code to production with continuous integration testing.
Pricing Structure: CircleCI offers a range of pricing plans based on the number of concurrent jobs and parallelism required for projects. Heroku CI, on the other hand, is included as part of the Heroku platform and pricing is based on the resources consumed by the overall application, including CI testing.
Scalability: CircleCI is known for its scalability and ability to handle large-scale projects with ease, thanks to its distributed infrastructure. Heroku CI is suitable for smaller to medium-sized projects that are hosted on the Heroku platform, providing a more streamlined integration for these applications.
Customization and Flexibility: CircleCI provides a high degree of customization and flexibility in configuring the CI/CD pipelines, allowing users to define custom workflows and conditions. While Heroku CI offers some flexibility, it is more tailored towards the Heroku platform's conventions and may have fewer customization options compared to CircleCI.
Third-party Integrations: CircleCI has a wide range of third-party integrations available in its marketplace, allowing users to extend its functionality with additional tools and services. Heroku CI, being part of the Heroku ecosystem, is closely integrated with Heroku's own services and may have limited options for third-party integrations.

In Summary, CircleCI and Heroku CI differ in their primary focus, integration capabilities, pricing structure, scalability, customization options, and third-party integrations.

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 CircleCI, Heroku CI

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

Phillip

Developer at Coach Align

Mar 18, 2021

Decided

The introduction of Orbs a few years ago has really streamlined CircleCI configuration files and made them really easy to work with. Haven't tried GitHub Actions and decided to go with what was familiar instead of trying something new. Tried to make AWS Codepipeline work a few years back on different projects and found it to be incredibly frustrating, lacking support for some of the most basic features and use cases.

41.1k views41.1k

Comments

Felipe

May 24, 2020

Needs advice

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

198k views198k

Comments

Detailed Comparison

CircleCI	Heroku CI
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.	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.
Language-Inclusive Support;Custom Environments;Flexible Resource Allocation;SSH Or Local Builds For Easy Debugging;Improved Caching;Unmatched Security;Parallelism;Insights	-
Statistics
Stacks 14.5K	Stacks 90
Followers 7.1K	Followers 132
Votes 974	Votes 5
Pros & Cons
Pros 226 Github integration 177 Easy setup 153 Fast builds 94 Competitively priced 74 Slack integration Cons 12 Unstable 6 Scammy pricing structure 0 Aggressive Github permissions	Pros 3 No waiting in the queue 1 Best in class pipeline integration 1 Consolidated Heroku billing
Integrations
dotCloud GitHub Xcode Azure Container Service Slack Heroku JavaScript Node.js Python Amazon EC2	Heroku GitHub

What are some alternatives to CircleCI, Heroku CI?

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.

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.

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.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Related Comparisons

CircleCI vs Heroku CI: What are the differences?

Hosting Platform: CircleCI is primarily a continuous integration and delivery platform, while Heroku CI is a continuous integration service provided by Heroku, a platform as a service (PaaS) provider. CircleCI is focused on automating the build, test, and deploy processes, while Heroku CI is an extension of the Heroku platform that allows for continuous integration.
Integration with Other Services: CircleCI integrates seamlessly with popular version control systems like GitHub and Bitbucket, as well as other services such as Slack for notifications. On the other hand, Heroku CI is tightly integrated with the Heroku platform, streamlining the process of deploying code to production with continuous integration testing.
Pricing Structure: CircleCI offers a range of pricing plans based on the number of concurrent jobs and parallelism required for projects. Heroku CI, on the other hand, is included as part of the Heroku platform and pricing is based on the resources consumed by the overall application, including CI testing.
Scalability: CircleCI is known for its scalability and ability to handle large-scale projects with ease, thanks to its distributed infrastructure. Heroku CI is suitable for smaller to medium-sized projects that are hosted on the Heroku platform, providing a more streamlined integration for these applications.
Customization and Flexibility: CircleCI provides a high degree of customization and flexibility in configuring the CI/CD pipelines, allowing users to define custom workflows and conditions. While Heroku CI offers some flexibility, it is more tailored towards the Heroku platform's conventions and may have fewer customization options compared to CircleCI.
Third-party Integrations: CircleCI has a wide range of third-party integrations available in its marketplace, allowing users to extend its functionality with additional tools and services. Heroku CI, being part of the Heroku ecosystem, is closely integrated with Heroku's own services and may have limited options for third-party integrations.

In Summary, CircleCI and Heroku CI differ in their primary focus, integration capabilities, pricing structure, scalability, customization options, and third-party integrations.

CircleCI vs Heroku CI

Overview