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

No cppcheck reports found if they stored in workspace

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      After the fix 9178, the report publisher is no longer able to find the reports if
      they were stored in the workspace directory because the plugin now starts the search
      from the module root instead of the workspace root.

        Attachments

          Activity

          Hide
          languitar Johannes Wienke added a comment -

          I can confirm this. We had to change our pattern to find the file.

          Show
          languitar Johannes Wienke added a comment - I can confirm this. We had to change our pattern to find the file.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Gregory
          Path:
          src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckBuildAction.java
          src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckPublisher.java
          src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java
          src/main/java/org/jenkinsci/plugins/cppcheck/config/CppcheckConfig.java
          src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/config.jelly
          http://jenkins-ci.org/commit/cppcheck-plugin/98289b4c51df96e41dc235c4e1a0fc0e98a76d58
          Log:
          Fixed JENKINS-11096

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Path: src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckBuildAction.java src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckPublisher.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java src/main/java/org/jenkinsci/plugins/cppcheck/config/CppcheckConfig.java src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/config.jelly http://jenkins-ci.org/commit/cppcheck-plugin/98289b4c51df96e41dc235c4e1a0fc0e98a76d58 Log: Fixed JENKINS-11096
          Hide
          gbois Gregory Boissinot added a comment -

          I added a checkbox to look for report files from the workspace
          Available in 1.0.2

          Show
          gbois Gregory Boissinot added a comment - I added a checkbox to look for report files from the workspace Available in 1.0.2
          Hide
          pibragh Pietro Braghieri added a comment -

          the plugin is now able to open the report stored into the workspace but is no longer possible to open the C/C++ files directly from the details table.The links to the files seem to be inactive. (I guess that the path still points to the wrong root)

          Show
          pibragh Pietro Braghieri added a comment - the plugin is now able to open the report stored into the workspace but is no longer possible to open the C/C++ files directly from the details table.The links to the files seem to be inactive. (I guess that the path still points to the wrong root)
          Hide
          c_welch Chris Welch added a comment -

          Cannot drill down to source file when report is in workspace and source is in module.

          Module level directory gets duplicated in the directory path formed by the reporter. Having the report generator go to the module level is very confusing because this is completely inconsistent with Jenkins default shell behaviour to work in the workspace not the workspace/module.

          The reporter should behave like all other Jenkins shell behaviours and be relative to the workspace.

          Also, the Publish cppcheck results is DOCUMENTED to work from the workspace level NOT the module level. Here is the text from the screen (I capitalized the problem):

          "Cppcheck must be configured to generate XML reports for this plugin to function. Fileset includes setting that specifies the generated cppcheck XML report files, such as */cppcheck-result-.xml. Basedir of the fileset is relative to the WORKSPACE ROOT. If no value is set, then the default **/cppcheck-result.xml is used. Be sure not to include any non-report files into this pattern."

          The reporter should be fixed to work from the WORKSPACE root like all other Jenkins operations.

          Show
          c_welch Chris Welch added a comment - Cannot drill down to source file when report is in workspace and source is in module. Module level directory gets duplicated in the directory path formed by the reporter. Having the report generator go to the module level is very confusing because this is completely inconsistent with Jenkins default shell behaviour to work in the workspace not the workspace/module. The reporter should behave like all other Jenkins shell behaviours and be relative to the workspace. Also, the Publish cppcheck results is DOCUMENTED to work from the workspace level NOT the module level. Here is the text from the screen (I capitalized the problem): "Cppcheck must be configured to generate XML reports for this plugin to function. Fileset includes setting that specifies the generated cppcheck XML report files, such as * /cppcheck-result- .xml. Basedir of the fileset is relative to the WORKSPACE ROOT. If no value is set, then the default **/cppcheck-result.xml is used. Be sure not to include any non-report files into this pattern." The reporter should be fixed to work from the WORKSPACE root like all other Jenkins operations.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java
          src/main/java/org/jenkinsci/plugins/cppcheck/config/CppcheckConfig.java
          src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/config.jelly
          http://jenkins-ci.org/commit/cppcheck-plugin/473c63380a329feb1fd59a26d312e7811bbeb901
          Log:
          Fix JENKINS-11096 - Always process from workspace

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java src/main/java/org/jenkinsci/plugins/cppcheck/config/CppcheckConfig.java src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/config.jelly http://jenkins-ci.org/commit/cppcheck-plugin/473c63380a329feb1fd59a26d312e7811bbeb901 Log: Fix JENKINS-11096 - Always process from workspace
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckBuildAction.java
          src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckPublisher.java
          http://jenkins-ci.org/commit/cppcheck-plugin/536884fab49d2401a2b7b0dac2f19c8a29f434bf
          Log:
          Fix JENKINS-11096 - Always process from workspace

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckBuildAction.java src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckPublisher.java http://jenkins-ci.org/commit/cppcheck-plugin/536884fab49d2401a2b7b0dac2f19c8a29f434bf Log: Fix JENKINS-11096 - Always process from workspace
          Hide
          mixalturek Michal Turek added a comment -

          Closing.

          Show
          mixalturek Michal Turek added a comment - Closing.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              pibragh Pietro Braghieri
            • Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: