-
Bug
-
Resolution: Fixed
-
Minor
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
- relates to
-
JENKINS-51014 Gatling plugin - publisher persists Run instance in config.xml
-
- Resolved
-
-
JENKINS-51013 PCT does not correctly update dependencies if there is a newer version requirement in a detached plugin
-
- Open
-
- links to
[JENKINS-50977] Gatling plugin - publisher persists PrintStream to the disk (JEP-200)
Labels | New: JEP-200 |
Link | New: This issue relates to JENKINS-51013 [ JENKINS-51013 ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "https://github.com/jenkinsci/gatling-plugin/pull/16 (Web Link)" [ 20508 ] |
Link |
New:
This issue relates to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |