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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: _unsorted
    • Labels:
    • 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
    • Similar Issues:

      Description

      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!

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          No problem

          Show
          oleg_nenashev Oleg Nenashev added a comment - No problem
          Hide
          rulate Ricardo Ulate added a comment -

          I confirmed that it was my mistake. Sorry for the confusion.

          • Ricardo
          Show
          rulate Ricardo Ulate added a comment - I confirmed that it was my mistake. Sorry for the confusion. Ricardo
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Ricardo Ulate OK, looking forward to get your response

          Show
          oleg_nenashev Oleg Nenashev added a comment - Ricardo Ulate OK, looking forward to get your response
          Hide
          rulate Ricardo Ulate added a comment -

          Thanks Oleg Nenashev, can we put this ticket on hold for a day or two... I wanted to give you a fresh log with everything but I'm having issues running the job. I'm starting to doubt whether this error still appeared after I upgraded the plugins or I got confused because the job was failing and looked at the wrong log. I'll get the job running again and either send you all the information I can or close this ticket. Sorry for the inconvenience and thanks.

          -Ricardo

          Show
          rulate Ricardo Ulate added a comment - Thanks Oleg Nenashev , can we put this ticket on hold for a day or two... I wanted to give you a fresh log with everything but I'm having issues running the job. I'm starting to doubt whether this error still appeared after I upgraded the plugins or I got confused because the job was failing and looked at the wrong log. I'll get the job running again and either send you all the information I can or close this ticket. Sorry for the inconvenience and thanks. -Ricardo
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Th plugin itself should not fail.
          There is a chance that PrintStream actually comes from another plugin, and Build Name Setter is just the first plugin calling save() for this run.

          Ricardo Ulate could you please provide the full build log, job configuration and the list of installed plugins?

          Show
          oleg_nenashev Oleg Nenashev added a comment - Th plugin itself should not fail. There is a chance that PrintStream actually comes from another plugin, and Build Name Setter is just the first plugin calling save() for this run. Ricardo Ulate could you please provide the full build log, job configuration and the list of installed plugins?

            People

            • Assignee:
              rulate Ricardo Ulate
              Reporter:
              rulate Ricardo Ulate
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: