Make the tar extraction of a JDK less verbose #3
Conversation
Currently we have to scroll through many pages of JDK installation tar output at the beginning on our job's console output. Specifically, jdk1.8.0_131 includes 1830 files that get traced out. The easiest solution seems to be to eliminate the verbose "v" option.
|
@JasonMathison Sorry I just noticed this, I did not have notifications turned on for the repo. The change seems ok to me, although I don't know if there was a reason that the Also just a heads up, I would highly encourage you to not use this installation option for the JDK tool in the first place. It is unreliable and can break at any time, and with the changes to Oracle's JDK licensing with JDK 11 we need to switch to use OpenJDK downloads, which will mean that Java 8 will no longer be available from this tool. It is generally better to install the JDK on your build agents in advance instead of installing it on-demand using Jenkins. If you really need to install it on-demand, then it is better to use something like the "Run a shell command installer" with a script that runs |
There was a problem hiding this comment.
Looks like that flag has been there since that code was initially added (jenkinsci/jenkins@219a4c5), so I would be surprised if removing it upset anyone.
|
Is possible to merge this @dwnusbaum ? :) |
|
Sure, I will merge and try to release sometime this week. FWIW in regards to your earlier JDK 10 comments, the issue and related ones have been reported and discussed in JENKINS-54522 and JENKINS-54305. I do not anticipate having time dedicated to work on those issues myself, but I am more than happy to review any PRs you submit (although I would still recommend trying to avoid this installation method as much as possible). |
|
Thanks for merging this in! I will pass along your suggestions about how we should install JDKs to our devops team. |
|
I just released version 1.2 of the plugin with this change. It should be live on the update center in a few hours. Thanks for the PR @JasonMathison! |
Currently we have to scroll through many pages of JDK installation tar output at the beginning on our job's console output. Specifically, jdk1.8.0_131 includes 1830 files that get traced out. The easiest solution seems to be to eliminate the verbose "v" option.