Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-54957

Investigate Impact of java.sql modularization on classic Jenkins modes

XMLWordPrintable

    • Jenkinsfile Runner 1.0-beta-6

      I discovered that Jenkinsfile Runner does not work reliably with Java 11 when there is a plugin using "java.sql" internally (JENKINS-54426). It impacts Pipeline Utility Steps (JENKINS-54355), and it will likely also impact Pipeline: Maven Plugin and other plugins: https://github.com/search?p=2&q=org%3Ajenkinsci+%22java.sql%22&type=Code . For JFR the most critical thing is Pipeline plugins, of course.  CC rsandell cleclerc

      We need to investigate whether the failing behavior is also possible on classic Jenkins instances

       

          [JENKINS-54957] Investigate Impact of java.sql modularization on classic Jenkins modes

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-52012 [ 191514 ]
          Oleg Nenashev made changes -
          Link New: This issue relates to JENKINS-54426 [ JENKINS-54426 ]
          Oleg Nenashev made changes -
          Link New: This issue relates to JENKINS-54355 [ JENKINS-54355 ]
          Oleg Nenashev made changes -
          Summary Original: Investigate Input of java.sql modularization on classic Jenkins modes New: Investigate Impact of java.sql modularization on classic Jenkins modes
          Oleg Nenashev made changes -
          Epic Link Original: JENKINS-52012 [ 191514 ] New: JENKINS-51805 [ 191255 ]
          Baptiste Mathus made changes -
          Labels Original: java11 New: java11 triaged
          Baptiste Mathus made changes -
          Labels Original: java11 triaged New: java11 scrub triaged
          Baptiste Mathus made changes -
          Component/s New: jenkinsfile-runner [ 24123 ]

          Baptiste Mathus added a comment - - edited

          > We need to investigate whether the failing behavior is also possible on classic Jenkins instances

          This has been analyzed by alecharp in JENKINS-54355 and it is not reproducible in a standard environment. Pipeline-utility-steps works perfectly fine on JDK11 without using any additional --add-modules ...,java.sql switch.

          We've seen this issue surface at least in PCT, in JFR, so my current suspicion is that this issue is triggered by a special classloading used there (JTH?).

          Baptiste Mathus added a comment - - edited > We need to investigate whether the failing behavior is also possible on classic Jenkins instances This has been analyzed by alecharp in JENKINS-54355 and it is not reproducible in a standard environment. Pipeline-utility-steps works perfectly fine on JDK11 without using any additional --add-modules ...,java.sql switch. We've seen this issue surface at least in PCT, in JFR, so my current suspicion is that this issue is triggered by a special classloading used there (JTH?).

            Unassigned Unassigned
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: