GitLab CI vs Heroku CI

Overview

GitLab CI

Stacks2.3K

Followers1.6K

Votes75

GitHub Stars0

Forks0

Heroku CI

Stacks90

Followers132

Votes5

GitLab CI vs Heroku CI: What are the differences?

Integration with the respective platforms: GitLab CI is tightly integrated with GitLab, enabling seamless collaboration and CI/CD workflows within the GitLab platform. On the other hand, Heroku CI is specifically designed for testing and continuous integration within the Heroku platform, offering a streamlined experience for deploying and testing applications on Heroku.
Customizability and flexibility: GitLab CI provides extensive customization options through its configuration files, allowing users to tailor their CI pipelines according to their specific requirements. In contrast, Heroku CI offers a more guided and simplified approach to continuous integration, with less focus on intricate configuration settings.
Scalability and pricing: GitLab CI is part of the GitLab platform, which offers both self-hosted and cloud-based options, providing flexibility in scaling CI/CD resources based on the project's needs. Heroku CI is primarily designed for deployment and testing on the Heroku platform, with pricing structures based on usage within the Heroku ecosystem.
Environment support: GitLab CI supports a wide range of operating systems and environments for testing and deployment, allowing users to work with diverse technology stacks. Heroku CI, on the other hand, is optimized for deploying and testing applications specifically on the Heroku platform, with a focus on seamless integration with Heroku's environment.
Community support and documentation: GitLab CI benefits from a robust community and extensive documentation, offering resources for troubleshooting, best practices, and feature updates. Heroku CI leverages the resources and knowledge base of the Heroku platform, with guides and support tailored towards developers working within the Heroku ecosystem.
Deployment automation: GitLab CI offers advanced deployment automation features, enabling users to automate the deployment process based on the CI pipeline results. Heroku CI focuses on testing and validation within the Heroku platform, with deployment automation options available through Heroku's deployment tools.

In Summary, GitLab CI and Heroku CI differ in their platform integrations, customization levels, scalability options, environment support, community resources, and deployment automation 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 GitLab CI, Heroku CI

Stratos

Jan 13, 2020

Needs advice

We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.

Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.

We primarily need:

Fast SBT builds (caching)
Low maintenance overhead (ideally serverless)
Everything as code

Ease of use

181k views181k

Comments

Anonymous

Feb 14, 2020

Decided

Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like:

Add repo
Click - Click - Click
You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.

157k views157k

Comments

Detailed Comparison

GitLab CI	Heroku CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.	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.
Statistics
GitHub Stars 0	GitHub Stars -
GitHub Forks 0	GitHub Forks -
Stacks 2.3K	Stacks 90
Followers 1.6K	Followers 132
Votes 75	Votes 5
Pros & Cons
Pros 22 Robust CI with awesome Docker support 13 Simple configuration 9 All in one solution 7 Source Control and CI in one place 5 Integrated with VCS on commit Cons 2 Works best with GitLab repositories	Pros 3 No waiting in the queue 1 Consolidated Heroku billing 1 Best in class pipeline integration
Integrations
GitLab	Heroku GitHub

What are some alternatives to GitLab CI, 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.

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.

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.

Related Comparisons

GitLab CI vs Heroku CI: What are the differences?

Integration with the respective platforms: GitLab CI is tightly integrated with GitLab, enabling seamless collaboration and CI/CD workflows within the GitLab platform. On the other hand, Heroku CI is specifically designed for testing and continuous integration within the Heroku platform, offering a streamlined experience for deploying and testing applications on Heroku.
Customizability and flexibility: GitLab CI provides extensive customization options through its configuration files, allowing users to tailor their CI pipelines according to their specific requirements. In contrast, Heroku CI offers a more guided and simplified approach to continuous integration, with less focus on intricate configuration settings.
Scalability and pricing: GitLab CI is part of the GitLab platform, which offers both self-hosted and cloud-based options, providing flexibility in scaling CI/CD resources based on the project's needs. Heroku CI is primarily designed for deployment and testing on the Heroku platform, with pricing structures based on usage within the Heroku ecosystem.
Environment support: GitLab CI supports a wide range of operating systems and environments for testing and deployment, allowing users to work with diverse technology stacks. Heroku CI, on the other hand, is optimized for deploying and testing applications specifically on the Heroku platform, with a focus on seamless integration with Heroku's environment.
Community support and documentation: GitLab CI benefits from a robust community and extensive documentation, offering resources for troubleshooting, best practices, and feature updates. Heroku CI leverages the resources and knowledge base of the Heroku platform, with guides and support tailored towards developers working within the Heroku ecosystem.
Deployment automation: GitLab CI offers advanced deployment automation features, enabling users to automate the deployment process based on the CI pipeline results. Heroku CI focuses on testing and validation within the Heroku platform, with deployment automation options available through Heroku's deployment tools.

In Summary, GitLab CI and Heroku CI differ in their platform integrations, customization levels, scalability options, environment support, community resources, and deployment automation capabilities.

GitLab CI vs Heroku CI

Overview