unixPb: Remove hyphen from Bootjdk symlinks

[Haroon-Khel]

• commit message has one of the standard prefixes
• faq.md updated if appropriate
• other documentation is changed or added (if applicable)
• playbook changes run through VPC or QPC (if you have access)
• VPC/QPC not applicable for this PR
• for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

ref #2912

In light of #2912 (comment), this pr should not be merged while we have an upcoming release. And I will test the difference that this pr makes to the symlinks in our build containers by running builds in those containers

[github-actions]

A block has been put on this Pull Request as this repository is temporarily under a code freeze due to an ongoing release cycle.

If this pull request needs to be merged during the release cycle then please comment /merge and a PMC member will be able to remove the block.

If the code freeze is over you can remove this block by commenting /thaw.

[Haroon-Khel]

Ive removed the hyphen from the windows symlinks

[Haroon-Khel]

Solaris has one bootjdk, /opt/csw/java/jdk1.7.0_80, so I dont think any change is required there. On AIX we use a different format, /usr/java{{ jdk }}_64, so at the moment I am not going to change that. Only linux, windows and mac have been updated in the playbooks, and the alpine and linux build containers

[Haroon-Khel]

Changes to the build scripts is here https://github.com/adoptium/temurin-build/pull/3992/files

[Haroon-Khel]

vpc https://ci.adoptium.net/job/VagrantPlaybookCheck/1984/console

[Haroon-Khel]

Latest vpc, without windows as that passed in the last one
https://ci.adoptium.net/job/VagrantPlaybookCheck/1988/console

[Haroon-Khel]

Latest vpc, https://ci.adoptium.net/job/VagrantPlaybookCheck/1995/console. Successes on the boxes it could connect to

[Haroon-Khel]

Without the hyphens in the symlinks the upstream configure is able to find the bootjdks without a problem, see #2912 (comment)

[sxa]

Initial comment - we can hopefully remove a lot of these definitions in the dockerfiles (and elsewhere) since we are now using the default locations expected by the openjdk build process which means we don't have to have them explicitly specified. Having said that I could be ok with leaving them in for now and removing them in a future date

[sxa]

Solaris has one bootjdk, /opt/csw/java/jdk1.7.0_80, so I dont think any change is required there. On AIX we use a different format, /usr/java{{ jdk }}_64, so at the moment I am not going to change that.

Interesting thought ... I wonder where the openjdk build process looks by default on those platforms?

[sxa]

Noting also that we have 50 machines in jenkins that have at least one _BOOT_DIR variable defined on them. Hopefully they can get cleared up too with these changes being made :-)

[karianna]

/thaw

Pull Request unblocked - code freeze is over.

[Haroon-Khel]

Im going to hold off on the windows changes. It looks like the upstream configure looks in C:\Program Files\Java/ (/cygdrive/c/Program Files/Java) which is where we already unpack the JDK on our machines

infrastructure/ansible/playbooks/AdoptOpenJDK_Windows_Playbook/roles/Java_install/tasks/main.yml

Line 37 in 822366e

dest: C:\Program Files\Java

and

infrastructure/ansible/playbooks/AdoptOpenJDK_Windows_Playbook/roles/Java8/tasks/main.yml

Line 27 in 822366e

dest: C:\Program Files\Java

[sxa]

Im going to hold off on the windows changes. It looks like the upstream configure looks in C:\Program Files\Java/ (/cygdrive/c/Program Files/Java) which is where we already unpack the JDK on our machines

Confirmed that it does indeed "just work" with our current setup 👍🏻

[Haroon-Khel]

Noting also that we have 50 machines in jenkins that have at least one _BOOT_DIR variable defined on them. Hopefully they can get cleared up too with these changes being made :-)

Ive removed the BOOT_DIR variables from jenkins nodes (as much as I could if more are found please let me know)