• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Component/s: performance-signature-dynatrace-plugin
• Labels:

  • java11
  • regression
  • triaged

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

Christoph Forster created issue - 2019-01-14 07:39

Christoph Forster made changes - 2019-01-14 07:47

Description

Original: 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.

New: 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

Collapse comment: Oleg Nenashev added a comment - 2019-01-14 12:31

Oleg Nenashev added a comment - 2019-01-14 12:31

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 batmat. The version comparison does not cover the case, and hence it blows up

Expand comment: Oleg Nenashev added a comment - 2019-01-14 12:31

Oleg Nenashev added a comment - 2019-01-14 12:31 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 batmat . The version comparison does not cover the case, and hence it blows up

Oleg Nenashev made changes - 2019-01-14 12:31

Component/s		New: core [ 15593 ]
Component/s	Original: performance-signature-dynatrace-plugin [ 21420 ]

Oleg Nenashev made changes - 2019-01-14 12:31

Labels

New: regression

Oleg Nenashev made changes - 2019-01-14 12:31

Priority

Original: Critical [ 2 ]

New: Blocker [ 1 ]

Oleg Nenashev made changes - 2019-01-14 12:32

Epic Link

New: JENKINS-51805 [ 191255 ]

Oleg Nenashev made changes - 2019-01-14 12:32

Assignee

Original: Raphael Pionke [ rpionke ]

Collapse comment: Baptiste Mathus added a comment - 2019-01-14 12:32

Baptiste Mathus added a comment - 2019-01-14 12:32

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

Expand comment: Baptiste Mathus added a comment - 2019-01-14 12:32

Baptiste Mathus added a comment - 2019-01-14 12:32 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

Collapse comment: Oleg Nenashev added a comment - 2019-01-14 12:37

Oleg Nenashev added a comment - 2019-01-14 12:37

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

 

Expand comment: Oleg Nenashev added a comment - 2019-01-14 12:37

Oleg Nenashev added a comment - 2019-01-14 12:37 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  

Load more newer events