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

Plugin can not be loaded anymore due to JDK Problems

    • Performance Signature 3.0.3

      I recently updated the Plugin to Version 3.0.2 - Now I get the following Error after my Jenkins Restart:

      Performance Signature: UI version 3.0.2
      You must update Java from version 1.8 to version 8 or later to run this plugin.

      Switching back to 3.0.1 solves this problem

      Jenkins ver. 2.158.
      JDK: 1.8.0_181-b13

          [JENKINS-55562] Plugin can not be loaded anymore due to JDK Problems

          forster_ch what is your Jenkins version please? Also what is the JVM version you're running Jenkins on? Answering all these will you and anyone fixing possible issues quicker

          Baptiste Mathus added a comment - forster_ch what is your Jenkins version please? Also what is the JVM version you're running Jenkins on? Answering all these will you and anyone fixing possible issues quicker

          Oleg Nenashev added a comment -

          The message comes from 2.158 (it is in https://github.com/jenkinsci/jenkins/pull/3016 ). So I believe forster_ch is on the latest weekly.

          Apart from Dynatrace plugin, there are "mailer" and "workflow-cps" plugins using the latest Plugin POM. It is enough to screw almost every instance if it happens on any JVM

           

          Oleg Nenashev added a comment - The message comes from 2.158 (it is in https://github.com/jenkinsci/jenkins/pull/3016 ). So I believe forster_ch is on the latest weekly. Apart from Dynatrace plugin, there are "mailer" and "workflow-cps" plugins using the latest Plugin POM. It is enough to screw almost every instance if it happens on any JVM  

          Hi, Yes I run on Jenkins ver. 2.158.
          JDK: 1.8.0_181-b13

          Christoph Forster added a comment - Hi, Yes I run on Jenkins ver. 2.158. JDK: 1.8.0_181-b13

          Oleg Nenashev added a comment -

          JENKINS-55575 would be the best way to offer proper version comparison in the Jenkins core.

          I tested the logic manually, and I cannot reproduce it with Mailer plugin and with Pipeline: CPS. Likely there is something with dependency check flags and the generated manifest data, checking

          Oleg Nenashev added a comment - JENKINS-55575 would be the best way to offer proper version comparison in the Jenkins core. I tested the logic manually, and I cannot reproduce it with Mailer plugin and with Pipeline: CPS. Likely there is something with dependency check flags and the generated manifest data, checking

          Oleg Nenashev added a comment -

          Oleg Nenashev added a comment - Minimum-Java-Version: 8 is defined in the manifest for the reported plugin. https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/ViewSource/releases/de/tsystems/mms/apm/performance-signature-dynatrace/3.0.2/performance-signature-dynatrace-3.0.2.hpi!/META-INF/MANIFEST.MF . Plugin POM 3.31 was used Minimum-Java-Version: 1.7 in Mailer: https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/ViewSource/releases/org/jenkins-ci/plugins/mailer/1.23/mailer-1.23.hpi!/META-INF/MANIFEST.MF . Plugin POM 3.32 was used  Minimum-Java-Version: 1.8 in Pipeline: Support: https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/ViewSource/releases/org/jenkins-ci/plugins/workflow/workflow-support/3.0/workflow-support-3.0.hpi!/META-INF/MANIFEST.MF . Plugin POM 3.32 was used There is no difference in Plugin POM which would explain the difference in the metadata https://github.com/jenkinsci/plugin-pom/compare/plugin-3.31...plugin-3.32 .

          Oleg Nenashev added a comment -

          Soo, it comes from https://github.com/jenkinsci/performance-signature-dynatrace-plugin/blob/master/pom.xml#L97 . "minimumJavaVersion=8" is explicitly defined in the plugin.

           

          I consider it as not-a-blocker then, because the default behavior of Plugin POM won't break. We still need to apply fixes in the core though

          Oleg Nenashev added a comment - Soo, it comes from https://github.com/jenkinsci/performance-signature-dynatrace-plugin/blob/master/pom.xml#L97 . "minimumJavaVersion=8" is explicitly defined in the plugin.   I consider it as not-a-blocker then, because the default behavior of Plugin POM won't break. We still need to apply fixes in the core though

          Oleg Nenashev added a comment -

          I have created https://github.com/jenkinsci/performance-signature-dynatrace-plugin/pull/5 with a workaround in the plugin. A fix on the core side is still needed IMHO

          Oleg Nenashev added a comment - I have created https://github.com/jenkinsci/performance-signature-dynatrace-plugin/pull/5 with a workaround in the plugin. A fix on the core side is still needed IMHO

          Jesse Glick added a comment -

          From my PoV this is simply a bug in the plugin and no change in core is needed.

          Jesse Glick added a comment - From my PoV this is simply a bug in the plugin and no change in core is needed.

          Jesse Glick added a comment -

          I intentionally changed the component from core to the plugin, as described above.

          Jesse Glick added a comment - I intentionally changed the component from core to the plugin, as described above.

          Oleg Nenashev added a comment -

          There was also a change in Maven HPI Plugin and Plugin POM. Starting from Plugin POM 3.33, it is possible to just set a "hpi.compatibleSinceVersion" property so that there is no need to override values anymore

          Oleg Nenashev added a comment - There was also a change in Maven HPI Plugin and Plugin POM. Starting from Plugin POM 3.33, it is possible to just set a "hpi.compatibleSinceVersion" property so that there is no need to override values anymore

            rpionke Raphael Pionke
            forster_ch Christoph Forster
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: