-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
Autodetect boot JDK location based on playbook defaults #2167
Conversation
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
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
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
1 similar comment
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
Needs more work as it's causing issues in VPC with JDK8 builds using JDK7 to boot
|
Could bootjdk location be added to the config files jdkX_pipeline_config.groovy? |
@sxa - Did you want to continue with this PR or are you happy to park it given our refactoring efforts? |
On my list for this week, but I don't believe this PR is part of the stuff that's going to be moved. This will make the build and infra a bit simpler, so I want it in :-) |
c5f7d49
to
061a758
Compare
I think a default could reasonably be made there. My interest in particular is making sure that if someone is trying to debug locally on a machine (so not running via the playbooks) that these scripts are as self-sufficient as possible, but I certainly wouldn't be averse to having them in another location too |
Not quite certain which VPC platforms are stable at the moment unfortunately so I've run two for this to be able to compare:
|
run tests |
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.
Indentations appear off after the removal of the following if block. Might be just GH's editor being funky with tabs however
# Any version above 8 (11 for now due to openjdk-build#1409
if [ "$JAVA_FEATURE_VERSION" -gt 11 ]; then
Oh hang on - you're talking about the AIX one specifically ... |
OK I've put the conditional back in for now - adjusting it should probably be the scope of a separate PR |
All of them actually. If you look at each file appears off after that if block has been removed. Mac for example: |
Signed-off-by: Stewart X Addison <[email protected]>
Signed-off-by: Stewart X Addison <[email protected]>
Signed-off-by: Stewart X Addison <[email protected]>
Signed-off-by: Stewart X Addison <[email protected]>
Signed-off-by: Stewart X Addison <[email protected]>
Signed-off-by: Stewart X Addison <[email protected]>
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.
Happy for this to go in - I'd like to see someone break this function out into a commonplace though to avoid duplication at some point
There a lot of cleaning up I'd like to do with these scripts but I'm focusing on usability for now. The directory that it selects is different for each platform which makes it more difficult to get advantages from unifying under a single function (unless we always installed into, day, /usr/local/java regardless of platform |
Merging and I'll run a JDK17 pipeline (which failed last night due to the freemarker version issue) in order to verify and fix if required. |
* Autodetect boot JDK location based on playbook defaults Signed-off-by: Stewart X Addison <[email protected]>
Draft PR to auto-set JDK_BOOT_DIR based on default locations symlinked by the ansible playbooks. This should remove the need to have JDKxx_BOOT_DIR definitions on the build machines in jenkins and reduce the number of times a boot JDK is downloaded dynamically during the builds
VPC run
Signed-off-by: Stewart X Addison [email protected]