Need advice about which tool to choose?Ask the StackShare community!
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.
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
I think I've tried most of the CI tools out there at some point. It took me a while to get around to Buildkite because at first I didn't see much point given it seemed like you had to run the agent yourself. Eventually it dawned on me why this approach was more ingenious than I realised:
Running my app in a production (or production-like) environment was already a solved problem, because everything was already in some form of "everything as code". Having a test environment where the only difference was adding the Buildkite agent was a trivial addition.
It means that dev/test/prod parity is simple to achieve and maintain. It's also proven to be much easier to support than trying to deal with the problems that come with trying to force an app to fit into the nuances and constraints that are imposed by the containers/runtime of a CI service. When you completely control all of the environment the tests are running in you define those constraints too. It's been a great balance between a managed service and the flexibility of running it yourself.
And while none of my needs have hit the scale of Shopify (I saw one of their engineers speak about it at a conference once, I can't find the video now though 😞) it's good to know I can scale out my worker nodes to hundreds of thousands of workers to reduce the time it takes for my tests to run.
I would recommend you to consider the JFrog Platform that includes JFrog Pipelines - it will allow you to manage the full artifact life cycle for your sbt, docker and other technologies, and automate all of your CI and CD using cloud native declarative yaml pipelines. Will integrate smoothly with all your other toolset.
more configurable to setup ci/cd: * It can provide caching when build sbt, just add this section to yml file * Easy to use, many documentation
Weakness: * Need use gitlab as repository to bring more powerful configuration
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: 1. Add repo 2. Click - Click - Click 3. 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.
Pros of GitLab CI
- Robust CI with awesome Docker support22
- Simple configuration13
- All in one solution9
- Source Control and CI in one place7
- Integrated with VCS on commit5
- Free and open source5
- Easy to configure own build server i.e. GitLab-Runner5
- Hosted internally2
- Built-in Docker Registry1
- Built-in support of Review Apps1
- Pipeline could be started manually1
- Enable or disable pipeline by using env variables1
- Gitlab templates could be shared across logical group1
- Easy to setup the dedicated runner to particular job1
- Built-in support of Kubernetes1
Pros of Heroku CI
- No waiting in the queue3
- Best in class pipeline integration1
- Consolidated Heroku billing1
Sign up to add or upvote prosMake informed product decisions
Cons of GitLab CI
- Works best with GitLab repositories2
