Skip to content
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

JDK11 is the new default #10

Merged
merged 1 commit into from Jan 22, 2021
Merged

JDK11 is the new default #10

merged 1 commit into from Jan 22, 2021

Conversation

mbarbero
Copy link
Member

No description provided.

Signed-off-by: Mikaël Barbero <mikael.barbero@eclipse-foundation.org>
@mbarbero mbarbero requested a review from fredg02 January 22, 2021 11:42
@mbarbero mbarbero merged commit 3d7c264 into master Jan 22, 2021
@mbarbero mbarbero deleted the jdk11-new-default branch January 22, 2021 12:58
@msohn
Copy link

msohn commented Jan 23, 2021

@mbarbero
Copy link
Member Author

Your build is relying on the default java installed on the agent which is not really a best practice (and can be broken whenever this default jdk change). We upgraded the default jdk in agents as this is the one running the agent's remoting code. This is done to align the jdk used to run Jenkins controller (aka master) and the agent). It's an internal change so we did not announced it.

In order to use a stable JDK, you should use the following directive in your build:

tool name: 'adoptopenjdk-hotspot-jdk8-latest', type: 'jdk'

The list of valid names for jdk tools can be found here https://wiki.eclipse.org/Jenkins#JDK

@mbarbero
Copy link
Member Author

mbarbero commented Jan 23, 2021

@msohn
Copy link

msohn commented Jan 23, 2021

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants