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

Cppcheck report XMLs field doesn't retain data after update to 1.22

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: In Review (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: cppcheck-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.131
      Red Hat Enterprise Linux Server release 6.9
      openjdk version "1.8.0_171"
    • Similar Issues:

      Description

      After upgrading the plugin to 1.22, when we add 'Publish Cppcheck results' as a post-build step in a multi-job, the 'Cppcheck report XMLs' field won't retain data after the job is saved. Reverting the plugin to 1.21 resolves the issue.

        Attachments

          Activity

          Hide
          tatery Ted Tatery added a comment -

          I have the same issue on two different Jenkins instances.

          Show
          tatery Ted Tatery added a comment - I have the same issue on two different Jenkins instances.
          Hide
          stiobhan Stefan Fleischmann added a comment -

          After updating from 1.21 to 1.23 I see unreadable data in the old data section in Jenkins for the projects that use cppcheck and I have to reconfigure each one of them.
          So this update effectively breaks existing projects.

          Looks like with this fix the data syntax was changed. Old config looks like this:

          [...]
            <publishers>
              <org.jenkinsci.plugins.cppcheck.CppcheckPublisher plugin="cppcheck@1.21">
                <cppcheckConfig>
                  <pattern>**/cppcheck-*.xml</pattern>
          [...]
          

          new config:

          [...]
            <publishers>
              <org.jenkinsci.plugins.cppcheck.CppcheckPublisher plugin="cppcheck@1.23">
                <config>
                  <pattern>**/cppcheck-*.xml</pattern>
          [...]
          

          Is it not possible to migrate the old data automatically?

          Show
          stiobhan Stefan Fleischmann added a comment - After updating from 1.21 to 1.23 I see unreadable data in the old data section in Jenkins for the projects that use cppcheck and I have to reconfigure each one of them. So this update effectively breaks existing projects. Looks like with this fix the data syntax was changed. Old config looks like this: [...] <publishers> <org.jenkinsci.plugins.cppcheck.CppcheckPublisher plugin= "cppcheck@1.21" > <cppcheckConfig> <pattern>**/cppcheck-*.xml</pattern> [...] new config: [...] <publishers> <org.jenkinsci.plugins.cppcheck.CppcheckPublisher plugin= "cppcheck@1.23" > <config> <pattern>**/cppcheck-*.xml</pattern> [...] Is it not possible to migrate the old data automatically?
          Hide
          marcosteffan Marco Steffan added a comment -

          Yes, the next version of the plugin will be able to migrate from <1.21 versions to current versions. I am currently working on that issue which is related to JENKINS-52854 which hast the same cause.

           

          Show
          marcosteffan Marco Steffan added a comment - Yes, the next version of the plugin will be able to migrate from <1.21 versions to current versions. I am currently working on that issue which is related to  JENKINS-52854  which hast the same cause.  

            People

            • Assignee:
              marcosteffan Marco Steffan
              Reporter:
              mike_klein_syna Mike Klein
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: