undefined | Better HN

0 pointsbvirb3y ago0 comments

We spend more on Heroku CI than we do running our app on Heroku and it's well worth it.

CI runs on (almost) the exact same platform as production and we don't have to maintain any of it. When Heroku removes a package from their base image it gets removed from CI and we know if it broke anything.

The pricing model is the same as running our app. Which means if 10 people want to run 10 branches on CI at the same, and each CI run runs 32 nodes in parallel, and takes ~15 min, Heroku gives us 3200 nodes and we pay to run them for 15 minutes. No waiting, no upgrading to a different tier, etc...

I don't see many other people talking about Heroku CI, and Heroku doesn't seem to push it that much in their marketing, so either it's only really amazing for our use case or people just don't know about it yet.

For us it was a lot cheaper than other options when you consider how costly sitting around waiting for CI to start is.

Anyways that would be really hard to leave for another platform.

0 comments

bradgessler3y ago

Yeah that sounds like an awesome CI! Fly won’t ship anything that integrated anytime soon because there’s so much great CIs out there now. What you will see is Fly integrating into CIs for deployment steps, which could be to a staging env per branch or a final deploy to production.

Here’s a sense of what that looks like: https://fly.io/docs/app-guides/continuous-deployment-with-gi...

This obviously doesn’t come close to the way Heroku does it and requires some effort. I have some ideas for fly CLI commands that would make setting up a basic CI a little easier, but again, not to the level Heroku is doing it.

j / k navigate · click thread line to collapse

0 comments

bradgessler3y ago

Here’s a sense of what that looks like: https://fly.io/docs/app-guides/continuous-deployment-with-gi...

j / k navigate · click thread line to collapse