Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac OS builds for Erlang/OTP releases #7658

Closed
starbelly opened this issue Sep 15, 2023 · 4 comments
Closed

Mac OS builds for Erlang/OTP releases #7658

starbelly opened this issue Sep 15, 2023 · 4 comments

Comments

@starbelly
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently Mac OS builds are not provided along with releases on github. This can be particularly problematic when it comes to CI. Specifically, AFAIK most of the community depends on brew to install erlang for Mac OS CI workflows and jobs.

This is sub-optimal as the brew method comes with a lot of dependencies, and as such has tendency to break.

Describe the solution you'd like

The OTP has workflows to test building of Erlang/OTP and uploads this artifact, as such I believe it would be possible to at least attach the tarball when the release is created. Github actions such as setup-beam could utilize this artifact to ease usage in CI for the ecosystem, and of course people could just download and unpack as needed.

Describe alternatives you've considered

It might be possible for parts of the community to take this on, but it feels quite natural per the above to keep it here.

Additional context

Examples of recent failed builds in the community :

rebar3
grisp toolchain

@paulo-ferraz-oliveira
Copy link
Contributor

@starbelly, it's worth mentioning @wojtekmach's work, in #5723, so we're close 😄

And I feel the pain, both for rebar3 (updated CI recently to fix brew-related stuff: erlang/rebar3#2826) and setup-beam, too (specifically erlef/setup-beam#54).

@paulo-ferraz-oliveira
Copy link
Contributor

As per what's mentioned in #5723, maybe one solution could be to poll erlang/otp, build the image and store it in GitHub, as a first step?

@starbelly
Copy link
Contributor Author

As per what's mentioned in #5723, maybe one solution could be to poll erlang/otp, build the image and store it in GitHub, as a first step?

That's doable, if for some reason this is problematic here, that's definitely a viable alternative solution though. Thanks for calling it out!

@starbelly
Copy link
Contributor Author

starbelly commented Sep 15, 2023

It's possible this should be closed as a duplicate. I totally forgot about that PR and the issue. Lukas's arguments against this are sound as well.

@starbelly starbelly closed this as not planned Won't fix, can't repro, duplicate, stale Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants