Build Name Setter Plugin 1.6.8 is still affected by JEP-200 in Jenkins 2.102+

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Minor
    • Component/s: _unsorted
    • Environment:
      Virtualization: vmware
      Operating System: CentOS Linux 7 (Core)
      CPE OS Name: cpe:/o:centos:centos:7
      Kernel: Linux 3.10.0-693.2.2.el7.x86_64
      Architecture: x86-64

      This is related to JENKINS-48944, but I get this error with the release where it is marked as fixed.

      I have:

      • Jenkins v2.104
      • build-name-setter v1.6.8

      Relevant section of the exception (see attachment for full exception)

      Set build name.
New build name is '#414 dev2 625d1c0fb80d12a4758463d40b631f2fb99d57ca'
FATAL: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class com.tikal.jenkins.plugins.multijob.MultiJobBuild
java.lang.UnsupportedOperationException: Refusing to marshal java.io.PrintStream for security reasons; see https://jenkins.io/redirect/class-filter/
	at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:530)

...

Caused: java.io.IOException
	at hudson.XmlFile.write(XmlFile.java:201)
	at hudson.model.Run.save(Run.java:1923)
	at hudson.model.Run.setDisplayName(Run.java:803)
	at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setDisplayName(BuildNameSetter.java:76)
	at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.access$000(BuildNameSetter.java:31)
	at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter$1.tearDown(BuildNameSetter.java:64)

      Cheers!

        1. exception.txt
          5 kB
          Ricardo Ulate

            Assignee:
            Ricardo Ulate
            Reporter:
            Ricardo Ulate
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: