Find alternative place for hosting OTP releases about heroku-buildpack-elixir HOT 7 CLOSED

Build when PR is sent to verify a version exists. Then build and push to S3
only when merged into master.
That automates verifying the version.

On Thu, Oct 22, 2015 at 1:46 PM, Michael Williams [email protected]
wrote:

It's also more easily audited as well.

Is your intent to build only when the pull-request is merged?

—
Reply to this email directly or view it on GitHub
#56 (comment)
.

from heroku-buildpack-elixir.

Currently 37 releases are hosted (17.0-18.1.3), taking up 2.25gb space where each release is ~60mb.

from heroku-buildpack-elixir.

@ericmj Tweeting this out to check if anyone would sponsor these.

from heroku-buildpack-elixir.

Have this script running on a Droplet kindly provided by @dikaio (as well as S3! 👍). Going to clean-up a few things and put it in a CRON job.

Solves that, I guess.

from heroku-buildpack-elixir.

@mtwilliams please hold off on this.

The plan is to have a list of versions in a text file in this repo. When a new version is released, anyone can send a PR and have a build up and running for that version. This eliminates the need for a droplet and a cron. Travis or CircleCI can take care of the builds.

I'll also most likely host this on my own S3 account since the expenses are very low.

from heroku-buildpack-elixir.

It's also more easily audited as well.

Is your intent to build only when the pull-request is merged, @HashNuke?

from heroku-buildpack-elixir.

Done. So closing issue :)

from heroku-buildpack-elixir.