Build weekly releases with Java 11 #233
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preparation for doing weekly releases with Java 11. This PR cannot be merged until after Jenkins core adopts Java 11 (currently scheduled for June for weekly releases). Implements Proposal A from jenkins-infra/helpdesk#2945 (comment). Additionally adds printing of the Java version being used to ease debugging.
Testing done
I did not run this actual Pipeline job, but I tested my syntax with the following simple job:
I verified that this simple job printed the expected values for
JAVA_HOME
andPATH
when run with bothweekly
andstable
as the input parameters.