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

Unmarshalling error after v9 upgrade

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • Jenkins 2.249.1 (newly upgraded from 2.235.5)
      Analysis Model API plugin v9.0.0 (newly upgraded from v8.3.1)
      OpenJDK 8u265

    Description

      After an upgrade to version 2.249.1 of Jenkins core and version 9 of the Analysis Model API plugin (both were done within minutes of each other), we could no longer view Checkstyle issues from builds that were run with the old versions (Jenkins v2.235.5 and Analysis Model API v8.3.1), receiving the following unmarshalling error:

      2020-09-11 12:54:34.720+0000 [id=507]	SEVERE	i.j.p.util.AbstractXmlStream#readXml: Failed to load /var/lib/jenkins/jobs/Android-QuickBuild-Preflight/builds/42727/checkstyle-new-issues.xml
      com.thoughtworks.xstream.converters.ConversionException: Cannot deserialize object with new readObject()/writeObject() methods
      ---- Debugging information ----
      class               : edu.hm.hafner.analysis.Report
      required-type       : edu.hm.hafner.analysis.Report
      converter-type      : com.thoughtworks.xstream.converters.reflection.SerializableConverter
      path                : /analysisReport
      line number         : 2
      version             : not available
      -------------------------------
      

      I've attached a more complete log with stacktrace and slightly anonymized versions of the Checkstyle XML files that were being read.

      I have worked around the issue for the time being by downgrading the Analysis Model API plugin to v8.3.1, which has allowed existing builds to display their warnings again. We did not have any builds run with the newer version of the plugin, so I cannot comment whether new builds would have their warnings displayed while old builds would not, but this is not an ideal situation even if it's the case.

      Given it is now working with Jenkins 2.249.1 and Analysis Model API v8.3.1, I suspect an issue in v9.0.0 of the plugin and not in the Jenkins upgrade.

      Attachments

        1. checkstyle-blames.xml
          0.1 kB
        2. checkstyle-fixed-issues.xml
          35 kB
        3. checkstyle-forensics.xml
          0.1 kB
        4. checkstyle-new-issues.xml
          35 kB
        5. checkstyle-outstanding-issues.xml
          0.2 kB
        6. jenkins.log
          30 kB

        Issue Links

          Activity

            There are no comments yet on this issue.

            People

              drulli Ulli Hafner
              mtughan Michael Tughan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: