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
Enhancement: Make installer release process more automated and idempotent #684
Comments
Tagging @jmjaffe37 (I know you've been writing some scripting for the Microsoft updates) is there anything you've done that might help the Temurin project with updating the files? |
@gdams I made a feature in a local repo which automatically updates the config files for DEB and RPM installer creation for a given organization. I haven't uploaded it yet since it relies on python and bash (and there isn't any python in this repo yet). Also, it would need to be modified for general use. If there is a desire for me to upload this script, I can do so when I have the time :) Other than that, I up streamed a feature that allows building DEB and RPM from local files, I don't think that is relevant to this conversation though. |
@jmjaffe37 if you could share that python script in this issue that would be a good starting point, don't feel like you need to do the work to generalise it but it would be good to not start from scratch. |
@gdams I just pinged you some links :) |
Summary
I propose that the process of composing and releasing installers be made both more automated, and more idempotent.
Details
Creating four large PRs with checksums (etc etc) invites error and takes time. Also, the resulting installer creation job has been identified as being "clunky", and unable to be rerun if it fails. Instead, various manual changes need to be made before the job can be restarted.
For this reason, and others, I propose that this process be reviewed for a greater degree of automation and idempotency.
Background
During a recent Release Champion meeting (minuted here), the installer creation and release process was identified as one of the blockers to a quick and efficient release. Also, if something goes wrong during certain parts of the process, excessive effort is required to restore things to a state where the process can be resumed.
Relevant Parties
@gdams, or one of his associates, may be working on increased automation for this process. As such, this may be a duplicate of another issue.
Any thoughts George?
The text was updated successfully, but these errors were encountered: