-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ci: Add otp_win.zip to releases #8729
Conversation
CT Test Results 1 files 11 suites 4m 34s ⏱️ Results for commit da2159f. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
@@ -614,7 +626,7 @@ jobs: | |||
run: | | |||
shopt -s nullglob | |||
cd artifacts | |||
FILES=$(ls {*.tar.gz,*.txt}) | |||
FILES=$(ls {*.tar.gz,*.zip,*.txt}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at the moment the .zip is not yet included in the release, I'm not sure how .exe ends up here. I assume it's via some actions/download-artifact
but I couldn't figure it out. Any help would be appreciated.
The windows .exe and .dll files attached to each release are not created by GitHub actions, but our internal scripts. This because they need to be signed with our certificate and we cannot do that using GitHub actions. So if we want to have .zip for windows we either need to re-package the installer added by the sync releases GitHub action, or add the appropriate scripts to our internal ci that uploads it to erlang.org/downloads. I’ll try to get back to you next week to see if/how we can solve this. |
Yea, I have the same use case as @wojtekmach. I plan to support Windows in https://github.com/tsloughter/beamup/ and use the binary releases and being able to just unzip the release would be nice. |
We don't mind having this functionality so would welcome a PR that adds it. I suggest that it is done by creating a new github workflow that triggers on release creation+edit that downloads the windows installers (32 and 64-bit), installs them and then creates .zip files from what is installed. The same workflow could also be triggered on dispatch to create .zip files for any release that has already been released. |
@garazdawi my understanding is UNIX installations are relocatable since a few releases but windows aren't. In my testing, after I moved the installation directory, I couldn't run Perhaps making it relocatable is a first step towards this? |
There is a file called We will create a PR that removes this file from the installer. From what we can tell it is no longer needed and just causes problems. |
@garazdawi oh, perfect, I just removed erl.ini and it fixed the issue. Thanks! I'll open up a new PR per your instructions. |
I created a follow-up PR: #8787 |
I'd like to propose including Windows .zip release besides the .exe installer in GitHub releases.
I'm building a CLI tool that allows easily installing multiple OTP versions. I'd prefer not to use the installers for the following reasons:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Erlang OTP
andHKCR ".erl"
.After downloading the .zip, users can manually run the included
Install.exe
.Btw, the release requires vc_redist.x64.exe (also mentioned in #8531) so if this proposal is accepted, the question is whether it should be included in the .zip.
FWIW, in my tool I'm downloading and running it myself:
Another idea for not writing to windows registry would be to add a flag to generated installer, we can allegedly read it with
${GetParameters} $R0
, something it would perhaps be something likeotp_win64_27.1.exe /NOWINREG
.cc @tsloughter