• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: cloudcoreo-deploytime-plugin
• Labels:

  • JEP-200

[JENKINS-50978] CloudCoreo Deploy Wrapper and publisher persist PrintStream to the disk (JEP-200)

Oleg Nenashev created issue - 2018-04-24 23:37

Oleg Nenashev made changes - 2018-04-24 23:37

Component/s		New: cloudcoreo-deploytime-plugin [ 23176 ]
Component/s	Original: gatling-plugin [ 17479 ]

Oleg Nenashev made changes - 2018-04-24 23:38

Description

Original: According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/gatling-plugin/blob/775b494c4ba020018d0aef24316f844e47e0bb32/src/main/java/io/gatling/jenkins/GatlingPublisher.java#L44 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: * Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ * JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers

New: According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: * Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ * JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers

Oleg Nenashev made changes - 2018-04-24 23:38

Assignee

New: Andrew Armaneous [ armaneous ]

Oleg Nenashev made changes - 2018-04-24 23:38

Description

Original: According to the code inspection, there is a JEP-200 issue in the plugin: https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: * Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ * JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers

New: According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36 * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoPublisher.java#L33 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: * Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ * JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers

Oleg Nenashev made changes - 2018-04-24 23:38

Summary

Original: CloudCoreo Deploy Wrapper persists PrintStream to the disk (JEP-200)

New: CloudCoreo Deploy Wrapper and publisher persist PrintStream to the disk (JEP-200)

Oleg Nenashev made changes - 2018-04-24 23:39

Description

Original: According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36 * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoPublisher.java#L33 This code likely causes a JEP-200 issue when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: * Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ * JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers

New: According to the code inspection, there is a JEP-200 issue in the plugin: * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoBuildWrapper.java#L36 * https://github.com/jenkinsci/cloudcoreo-deploytime-plugin/blob/4be75455a056a0fb80ad14cd544e608956775153/src/main/java/com/cloudcoreo/plugins/jenkins/CloudCoreoPublisher.java#L33 This code likely causes a JEP-200 security exception when the object gets persisted to the disk. "java.io.PrintStream" is not whitelisted in Jenkins for a reason, because loggers are not expected reliably after being deserialized from the disk. Useful links about JEP-200: * Blog post for users: https://jenkins.io/blog/2018/03/15/jep-200-lts/ * JEP-200 guidelines for plugin developers: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers