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

JEP-200: ConversionException: Refusing to unmarshal logPrefixCache

    Details

    • Similar Issues:

      Description

      I'm getting lots of "Unreadable data" from different pipelines after upgrade to 2.107.1.

      ConversionException: Refusing to unmarshal logPrefixCache for security reasons; see https://jenkins.io/redirect/class-filter/ ---- Debugging information ---- class : com.google.common.cache.LocalCache$LocalLoadingCache required-type : com.google.common.cache.LocalCache$LocalLoadingCache converter-type : hudson.util.XStream2$BlacklistedTypesConverter path : /flow-build/logPrefixCache line number : 214 -------------------------------

      line numbers: 134, 214, 222, 238, 313, 391 etc.

      On first look log seems to be normal for mentioned build numbers. Is this something that I need to be worried about?

        Attachments

          Issue Links

            Activity

            nekto Marian Klymov created issue -
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Likely it happens for historical builds. Jesse Glick fixed persistency of the field in Pipeline: Job 2.0 (Feb 2016): https://github.com/jenkinsci/workflow-job-plugin/commit/6cdf41664d24e10c2f97d80f444571057fa2aa46

            Would it possible to confirm it? You could just open build.xml for the failing builds and check the version of the plugin for which the Run object has been saved.

            Show
            oleg_nenashev Oleg Nenashev added a comment - Likely it happens for historical builds. Jesse Glick fixed persistency of the field in Pipeline: Job 2.0 (Feb 2016): https://github.com/jenkinsci/workflow-job-plugin/commit/6cdf41664d24e10c2f97d80f444571057fa2aa46 Would it possible to confirm it? You could just open build.xml for the failing builds and check the version of the plugin for which the Run object has been saved.
            Hide
            nekto Marian Klymov added a comment -

            I've checked some of them. Indeed, they were using version before fix: workflow-job@1.13

            Show
            nekto Marian Klymov added a comment - I've checked some of them. Indeed, they were using version before fix: workflow-job@1.13
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Jesse Glick Andrew Bayer Sam Van Oort We could rename the cache field name to suppress these errors. The data would just go to the old data monitor then. WDYT?

            Show
            oleg_nenashev Oleg Nenashev added a comment - Jesse Glick Andrew Bayer Sam Van Oort We could rename the cache field name to suppress these errors. The data would just go to the old data monitor then. WDYT?
            Hide
            svanoort Sam Van Oort added a comment -

            Oleg Nenashev The field gets renamed in https://github.com/jenkinsci/workflow-job-plugin/pull/91 as part of fixing JENKINS-38383 – would that sort them out?

            Show
            svanoort Sam Van Oort added a comment - Oleg Nenashev The field gets renamed in https://github.com/jenkinsci/workflow-job-plugin/pull/91 as part of fixing JENKINS-38383 – would that sort them out?
            Hide
            svanoort Sam Van Oort added a comment -

            PR that should sort this out incidentally while fixing another bug IIUC

            Show
            svanoort Sam Van Oort added a comment - PR that should sort this out incidentally while fixing another bug IIUC
            svanoort Sam Van Oort made changes -
            Field Original Value New Value
            Remote Link This issue links to "Workflow-job #91 (Web Link)" [ 20310 ]
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Sam Van Oort Yes, the PR will do its job

            Show
            oleg_nenashev Oleg Nenashev added a comment - Sam Van Oort Yes, the PR will do its job
            Hide
            jglick Jesse Glick added a comment -

            Oleg Nenashev actually the fix was in 1.14-beta-1: original commit

            Show
            jglick Jesse Glick added a comment - Oleg Nenashev actually the fix was in 1.14-beta-1: original commit
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-38383 [ JENKINS-38383 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Jesse Glick thanks! I forgot to check the old repository. I have added information about this minor issue to https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200

            Show
            oleg_nenashev Oleg Nenashev added a comment - Jesse Glick thanks! I forgot to check the old repository. I have added information about this minor issue to https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200
            abayer Andrew Bayer made changes -
            Assignee Sam Van Oort [ svanoort ]
            Hide
            svanoort Sam Van Oort added a comment -

            Released with v2.19

            Show
            svanoort Sam Van Oort added a comment - Released with v2.19
            svanoort Sam Van Oort made changes -
            Status In Review [ 10005 ] Closed [ 6 ]
            Resolution Fixed [ 1 ]
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "CloudBees Internal CLTS-2942 (Web Link)" [ 20527 ]

              People

              • Assignee:
                svanoort Sam Van Oort
                Reporter:
                nekto Marian Klymov
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: