|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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.
Given that the problem seems to be in the deserialization of those files, I was thinking that given the files, and your knowledge of the code base, you could run them through the deserialization process and hopefully reproduce the problem. Not the case?
I tried to trace through the deserialization process with my debugger attached to the affected machine but, in the time I had, I was not able to get my head around the deserialization code sufficient to understand what was going on.
Would a comprehensive list of all plugins installed on the box help? A copy of its config.xml file? Not sure what are the relevant details.