• Type: New Feature
• Resolution: Unresolved
• Priority: Minor
• Component/s: core, jdk-tool-plugin
• Labels:

  • automatic-install
  • java_home

1. 

   screenshot-1.png

   95 kB

   2019-08-03 09:36

[JENKINS-54959] Offer a new Unarchive installer which takes Java archive structure into account

Benoit Le Gall created issue - 2018-11-30 08:25

Benoit Le Gall made changes - 2018-11-30 08:30

URL

Original: https://stackoverflow.com/questions/53519831/jenkins-pipeline-withmaven-can-not-resolve-java-home

New: https://stackoverflow.com/q/53519831/244911

Benoit Le Gall made changes - 2018-11-30 13:35

Description

Original: *Jenkins installation* Installed from docker image [jenkinsci/docker - README.me|https://github.com/jenkinsci/docker/blob/master/README.md] *Configuration - configureTools*  # JDK :  ** name : Java 10  ** install automatically : true (extract *.zip/*.tar.gz)  ** url : [https://download.java.net/java/GA/jdk10/10.0.2/19aef61b38124481863b1413dce1855f/13/openjdk-10.0.2_linux-x64_bin.tar.gz]  # Maven :  ** name : Default  ** install automatically : true (Install from Apache)  ** version : 3.6.0 *Jenkinsfile*  {code:groovy} pipeline {     agent any     stages {         stage('Clean') {             steps {                 withMaven(maven: 'Default',jdk: 'Java 10') {                     sh "echo JAVA_HOME=$JAVA_HOME"                     sh "mvn clean"                 }             }         }     } } {code} *Error* {noformat} [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline]\{ (Clean) [Pipeline] withMaven [withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation Java 10 [withMaven] using Maven installation 'Default' [Pipeline] { [Pipeline] sh + echo 'JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10' JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10 [Pipeline] sh + mvn clean -B -V ----- withMaven Wrapper script ----- The JAVA_HOME environment variable is not defined correctly This environment variable is needed to run this program NB: JAVA_HOME should point to a JDK not a JRE [Pipeline] } {noformat} *Actual*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10_ *Expected*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10/*jdk-10.0.2*_ Looks like the automatic set JEVA_HOME is missing the last part of the path

New: *Jenkins installation* Installed from docker image [jenkinsci/docker - README.me|https://github.com/jenkinsci/docker/blob/master/README.md] *Plugins* [Pipeline Maven Plugin|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin] *Configuration - configureTools*  # JDK :  ** name : Java 10  ** install automatically : true (extract *.zip/*.tar.gz)  ** url : [https://download.java.net/java/GA/jdk10/10.0.2/19aef61b38124481863b1413dce1855f/13/openjdk-10.0.2_linux-x64_bin.tar.gz]  # Maven :  ** name : Default  ** install automatically : true (Install from Apache)  ** version : 3.6.0 *Jenkinsfile*  {code:groovy} pipeline {     agent any     stages {         stage('Clean') {             steps {                 withMaven(maven: 'Default',jdk: 'Java 10') {                     sh "echo JAVA_HOME=$JAVA_HOME"                     sh "mvn clean"                 }             }         }     } } {code} *Error* {noformat} [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline]\{ (Clean) [Pipeline] withMaven [withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation Java 10 [withMaven] using Maven installation 'Default' [Pipeline] { [Pipeline] sh + echo 'JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10' JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10 [Pipeline] sh + mvn clean -B -V ----- withMaven Wrapper script ----- The JAVA_HOME environment variable is not defined correctly This environment variable is needed to run this program NB: JAVA_HOME should point to a JDK not a JRE [Pipeline] } {noformat} *Actual*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10_ *Expected*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10/*jdk-10.0.2*_ Looks like the automatic set JEVA_HOME is missing the last part of the path

Collapse comment: Oleg Nenashev added a comment - 2018-12-02 09:09

Oleg Nenashev added a comment - 2018-12-02 09:09

"Unzip" tool installer does not know anything specific about Java or any other tool. It just unpacks the archive to a tool cache and then sets home to the root of the archive. So it's not a bug.

In this case it might be helpful to create a new version of the installer in the JDK Tool Plugin. It can be done by copying or extending the https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java in the plugin

CC dnusbaum who maintains the plugin now

 

 

 

Expand comment: Oleg Nenashev added a comment - 2018-12-02 09:09

Oleg Nenashev added a comment - 2018-12-02 09:09 "Unzip" tool installer does not know anything specific about Java or any other tool. It just unpacks the archive to a tool cache and then sets home to the root of the archive. So it's not a bug. In this case it might be helpful to create a new version of the installer in the JDK Tool Plugin. It can be done by copying or extending the https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java  in the plugin CC dnusbaum who maintains the plugin now      

Oleg Nenashev made changes - 2018-12-02 09:10

Component/s

New: jdk-tool-plugin [ 23529 ]

Oleg Nenashev made changes - 2018-12-02 09:10

Issue Type

Original: Bug [ 1 ]

New: New Feature [ 2 ]

Oleg Nenashev made changes - 2018-12-02 09:11

Summary

Original: Automatically installed java set incorrect JAVA_HOME

New: Offer a new Unarchive installer which takes Java archive structure into account

Benoit Le Gall made changes - 2018-12-03 08:36

Description

Original: *Jenkins installation* Installed from docker image [jenkinsci/docker - README.me|https://github.com/jenkinsci/docker/blob/master/README.md] *Plugins* [Pipeline Maven Plugin|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin] *Configuration - configureTools*  # JDK :  ** name : Java 10  ** install automatically : true (extract *.zip/*.tar.gz)  ** url : [https://download.java.net/java/GA/jdk10/10.0.2/19aef61b38124481863b1413dce1855f/13/openjdk-10.0.2_linux-x64_bin.tar.gz]  # Maven :  ** name : Default  ** install automatically : true (Install from Apache)  ** version : 3.6.0 *Jenkinsfile*  {code:groovy} pipeline {     agent any     stages {         stage('Clean') {             steps {                 withMaven(maven: 'Default',jdk: 'Java 10') {                     sh "echo JAVA_HOME=$JAVA_HOME"                     sh "mvn clean"                 }             }         }     } } {code} *Error* {noformat} [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline]\{ (Clean) [Pipeline] withMaven [withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation Java 10 [withMaven] using Maven installation 'Default' [Pipeline] { [Pipeline] sh + echo 'JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10' JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10 [Pipeline] sh + mvn clean -B -V ----- withMaven Wrapper script ----- The JAVA_HOME environment variable is not defined correctly This environment variable is needed to run this program NB: JAVA_HOME should point to a JDK not a JRE [Pipeline] } {noformat} *Actual*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10_ *Expected*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10/*jdk-10.0.2*_ Looks like the automatic set JEVA_HOME is missing the last part of the path

New: *Jenkins installation* Installed from docker image [jenkinsci/docker - README.me|https://github.com/jenkinsci/docker/blob/master/README.md] *Plugins* [Pipeline Maven Plugin|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin] *Configuration - configureTools*  # JDK :  ** name : Java 10  ** install automatically : true (extract .zip/.tar.gz)  ** url : [https://download.java.net/java/GA/jdk10/10.0.2/19aef61b38124481863b1413dce1855f/13/openjdk-10.0.2_linux-x64_bin.tar.gz]  # Maven :  ** name : Default  ** install automatically : true (Install from Apache)  ** version : 3.6.0 *Jenkinsfile*  {code:groovy} pipeline {     agent any     stages {         stage('Clean') {             steps {                 withMaven(maven: 'Default',jdk: 'Java 10') {                     sh "echo JAVA_HOME=$JAVA_HOME"                     sh "mvn clean"                 }             }         }     } } {code} *Error* {noformat} [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline]\{ (Clean) [Pipeline] withMaven [withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation Java 10 [withMaven] using Maven installation 'Default' [Pipeline] { [Pipeline] sh + echo 'JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10' JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10 [Pipeline] sh + mvn clean -B -V ----- withMaven Wrapper script ----- The JAVA_HOME environment variable is not defined correctly This environment variable is needed to run this program NB: JAVA_HOME should point to a JDK not a JRE [Pipeline] } {noformat} *Actual*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10_ *Expected*  _JAVA_HOME=/var/jenkins_home/tools/hudson.model.JDK/Java_10/*jdk-10.0.2*_ Looks like the automatic set JEVA_HOME is missing the last part of the path

Collapse comment: Benoit Le Gall added a comment - 2018-12-03 14:39

Benoit Le Gall added a comment - 2018-12-03 14:39

Question: why isn't a default installer for open-jdk ?

Cause there is a plugin, but no more upgraded (openJDK-native-plugin) :/

Expand comment: Benoit Le Gall added a comment - 2018-12-03 14:39

Benoit Le Gall added a comment - 2018-12-03 14:39 Question: why isn't a default installer for open-jdk ? Cause there is a plugin, but no more upgraded ( openJDK-native-plugin ) :/

Collapse comment: Oleg Nenashev added a comment - 2018-12-03 14:45

Oleg Nenashev added a comment - 2018-12-03 14:45

Historical reasons. I believe that part of the code was originally written for Sun JVMs, maybe before OpenJDK was formalized and established

Expand comment: Oleg Nenashev added a comment - 2018-12-03 14:45

Oleg Nenashev added a comment - 2018-12-03 14:45 Historical reasons. I believe that part of the code was originally written for Sun JVMs, maybe before OpenJDK was formalized and established

Load more newer events