[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Sam Van Oort updated JENKINS-50350 Released with v2.19 Jenkins / JENKINS-50350 JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Change By: Sam Van Oort Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Andrew Bayer assigned an issue to Sam Van Oort Jenkins / JENKINS-50350 JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Change By: Andrew Bayer Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache 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 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev updated JENKINS-50350 Jenkins / JENKINS-50350 JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev started work on JENKINS-50350 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Jesse Glick commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Oleg Nenashev actually the fix was in 1.14-beta-1: original commit Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Sam Van Oort Yes, the PR will do its job Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Sam Van Oort commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache PR that should sort this out incidentally while fixing another bug IIUC Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Sam Van Oort commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache 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? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache 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? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Marian Klymov commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache I've checked some of them. Indeed, they were using version before fix: workflow-job@1.13 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Marian Klymov created an issue Jenkins / JENKINS-50350 JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2018-03-22 20:26 Environment: Jenkins 2.107.1 Pipeline: Job 2.17 Labels: JEP-200 log pipeline Priority: Minor Reporter: Marian Klymov 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?