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

Plugin can not be loaded anymore due to JDK Problems

    Details

    • Similar Issues:
    • Released As:
      Performance Signature 3.0.3

      Description

      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

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            In https://github.com/jenkinsci/performance-signature-dynatrace-plugin/commit/8a1b6d306caac6148c103e90a2e690a9f26af61d  the pom.xml was updated to 3.30+. It included the minimum Java version requirement.

             

            I believe the latest Jenkins weekly with https://github.com/jenkinsci/jenkins/pull/3016 is used, CC Baptiste Mathus. The version comparison does not cover the case, and hence it blows up

            Show
            oleg_nenashev Oleg Nenashev added a comment - In https://github.com/jenkinsci/performance-signature-dynatrace-plugin/commit/8a1b6d306caac6148c103e90a2e690a9f26af61d   the pom.xml was updated to 3.30+. It included the minimum Java version requirement.   I believe the latest Jenkins weekly with https://github.com/jenkinsci/jenkins/pull/3016 is used, CC Baptiste Mathus . The version comparison does not cover the case, and hence it blows up
            Hide
            batmat Baptiste Mathus added a comment -

            Christoph Forster 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

            Show
            batmat Baptiste Mathus added a comment - Christoph Forster 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
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            The message comes from 2.158 (it is in https://github.com/jenkinsci/jenkins/pull/3016 ). So I believe Christoph Forster 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

             

            Show
            oleg_nenashev Oleg Nenashev added a comment - The message comes from 2.158 (it is in https://github.com/jenkinsci/jenkins/pull/3016 ). So I believe Christoph Forster 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  
            Hide
            forster_ch Christoph Forster added a comment -

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

            Show
            forster_ch Christoph Forster added a comment - Hi, Yes I run on Jenkins ver. 2.158. JDK: 1.8.0_181-b13
            Hide
            oleg_nenashev 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

            Show
            oleg_nenashev 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
            Show
            oleg_nenashev 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 .
            Hide
            oleg_nenashev 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

            Show
            oleg_nenashev 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
            Hide
            oleg_nenashev 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

            Show
            oleg_nenashev 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
            Hide
            jglick Jesse Glick added a comment -

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

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

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

            Show
            jglick Jesse Glick added a comment - I intentionally changed the component from core to the plugin, as described above.
            Hide
            oleg_nenashev 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

            Show
            oleg_nenashev 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

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: