-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
create_installer_windows failing with new "temurin" variant support #438
Conversation
…optium#437) Signed-off-by: Stewart X Addison <[email protected]>
@gdams Any idea what's going on with the checks here? Is http://s.sudre.free.fr/ a legitimate source (if nothing else it seems a bit wrong that it's not https)
|
@sxa I'm not entirely sure what's broken, the cask was updated 10 days ago (https://github.com/Homebrew/homebrew-cask/blob/master/Casks/packages.rb) so I wonder if the link is broken, I'll try running it again |
Hmm seems ok this time. Hopefully x64 will go through ok too ... |
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.
lgtm
@@ -70,6 +70,10 @@ IF NOT "%ARCH%" == "x64" ( | |||
) | |||
) | |||
|
|||
REM Update to handle the change of build variant until implications | |||
REM of setting this to Temurin can be evaluated | |||
IF "%JVM%" == "temurin" SET JVM=hotspot |
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.
@sxa, @karianna Why this special case is not handled on the caller side ?
temurin is not a JVM so the JVM arg must not accept "temurin" and hide some other value behind ..
If you set upsteam a vendor name temurin , his place is in VENDOR_BRANDING from this script, not in JVM arg
I think in caller job you must do somthing like that:
if (VARIANT == "temurin" )
VENDOR_BRANDING"=Temurin"
JVM="hotspot" // default JVM for VARIANT "temurin"
call createInstallerJob
fi
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.
The intention of the initial set of changes was to do the minimum required in the pipelines to enable the use of a temurin variant. There will likely be subsequent changes to split this out using other variables but initially this was the simplest option to prove that we could split out hotspot and temurin. After implementing it, we hit this issue and this was the simplest way to fix it which wouldn't involve any risk to changing the contents of the package.
I agree this could be switched to being done in the calling pipelines, and so your proposed change can be covered in the other issue which Martijn has created :-)
Fix for the following error in create_installer_windows:
This just maps
JVM=temurin
toJVM=hotspot
to ensure all the values are the same as before. Happy to entertain a discussion on whether this should be changed in the future but for now this should allow the installer to be generated the same as it was before the changes.Signed-off-by: Stewart X Addison [email protected]