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

JEP-200: ConversionException: Refusing to unmarshal logPrefixCache

    XMLWordPrintable

Details

    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

            oleg_nenashev Oleg Nenashev added a comment -

            Likely it happens for historical builds. jglick 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.

            oleg_nenashev Oleg Nenashev added a comment - Likely it happens for historical builds. jglick 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.
            nekto Marian Klymov added a comment -

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

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

            jglick abayer svanoort We could rename the cache field name to suppress these errors. The data would just go to the old data monitor then. WDYT?

            oleg_nenashev Oleg Nenashev added a comment - jglick abayer svanoort We could rename the cache field name to suppress these errors. The data would just go to the old data monitor then. WDYT?
            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?

            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?
            svanoort Sam Van Oort added a comment -

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

            svanoort Sam Van Oort added a comment - PR that should sort this out incidentally while fixing another bug IIUC
            oleg_nenashev Oleg Nenashev added a comment -

            svanoort Yes, the PR will do its job

            oleg_nenashev Oleg Nenashev added a comment - svanoort Yes, the PR will do its job
            jglick Jesse Glick added a comment -

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

            jglick Jesse Glick added a comment - oleg_nenashev actually the fix was in 1.14-beta-1: original commit
            oleg_nenashev Oleg Nenashev added a comment -

            jglick 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

            oleg_nenashev Oleg Nenashev added a comment - jglick 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
            svanoort Sam Van Oort added a comment -

            Released with v2.19

            svanoort Sam Van Oort added a comment - Released with v2.19

            People

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

              Dates

                Created:
                Updated:
                Resolved: