• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • jdk-tool-plugin
    • All

      As of today, all of our java 10 builds no longer work (they did yesterday).

       

      In our pipeline we have:

       

       

      stage('Build') {
                  tools {    
                  jdk 'JDK10'   
          }         
      }
      

       

       

      And at runtime 
      Java version: 9.0.4, vendor: Oracle Corporation, runtime:
      is ultimately being used. 

       

      I noticed in the JDK tools provided config in the jenkins admin pane that jdk 10 is no longer an option. Latest is now 9.0.4, which I presume is the root cause. 

       

      Is there anything that can be done at the plugin provider level, or is this something Oracle related or licensing?

       

       

       

       

       

          [JENKINS-55482] JDK 10 no longer working

          Devin Nusbaum added a comment -

          The problem is that the layout of Oracle's website has changed, which broke the crawler on the Jenkins infra side. See JENKINS-54305 for additional details, in short, we want to deprecate the current jdk tool entirely, and to perhaps replace it by using AdoptOpenJDK.

          For now, the only workarounds I know of are to preinstall the JDK on your agents so you don't need to use Jenkins to install the JDK, or to use the "Run Shell Command" installer method instead of "Download from java.sun.com" and run something like "apt-get install openjdk11" or similar.

          I am a little surprised that you only started seeing this today, and not earlier, but maybe it coincided with an update on your side?

          Devin Nusbaum added a comment - The problem is that the layout of Oracle's website has changed, which broke the crawler on the Jenkins infra side. See  JENKINS-54305 for additional details, in short, we want to deprecate the current jdk tool entirely, and to perhaps replace it by using AdoptOpenJDK. For now, the only workarounds I know of are to preinstall the JDK on your agents so you don't need to use Jenkins to install the JDK, or to use the "Run Shell Command" installer method instead of "Download from java.sun.com" and run something like "apt-get install openjdk11" or similar. I am a little surprised that you only started seeing this today, and not earlier, but maybe it coincided with an update on your side?

          David Goate added a comment -

          Perhaps, it could be that one of our slaves got re-provisioned as we use the EC2 plugin to start and stop slaves - perhaps one today got re-provisioned.

           

          We have for now stopped using the tool and migrated to using JDK 11 with a custom tool installer. Our pipelines now look like this:

           

          pipeline {   
           agent {        label 'cloud-slave'    }   
            environment {       
            JDK_11 = tool name: 'JDK11', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool'        
            JAVA_HOME = "${env.JDK_11}"    
            }
          ...
          }

          Which seems to be working. All it required was the set up of a customer tool (see attached image)

           

           

           

          David Goate added a comment - Perhaps, it could be that one of our slaves got re-provisioned as we use the EC2 plugin to start and stop slaves - perhaps one today got re-provisioned.   We have for now stopped using the tool and migrated to using JDK 11 with a custom tool installer. Our pipelines now look like this:   pipeline { agent { label 'cloud-slave' } environment { JDK_11 = tool name: 'JDK11' , type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool' JAVA_HOME = "${env.JDK_11}" } ... } Which seems to be working. All it required was the set up of a customer tool (see attached image)      

            Unassigned Unassigned
            davidgoate David Goate
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: