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

Missing links to source in cppcheck plugin

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Component/s: cppcheck-plugin
    • Labels:
      None
    • Environment:
      Ubuntu 10.04
    • Similar Issues:

      Description

      In the Details table of the CppCheck results page for a job, I have a number of issues listed. However, there are no links to the source code from the highlighted issues. Is that a bug or a limitation of the CppCheck plugin?

      Version details:
      CppCheck plugin 1.15
      Jenkins 1.554,

        Attachments

          Activity

          Hide
          mixalturek Michal Turek added a comment -

          Hi, can you attach a screenshot? The issues that were in the previous build but are solved in the current build (the green ones) doesn't contain the link, it is a "feature". It would require a change of data model and was just too difficult to implement.

          Show
          mixalturek Michal Turek added a comment - Hi, can you attach a screenshot? The issues that were in the previous build but are solved in the current build (the green ones) doesn't contain the link, it is a "feature". It would require a change of data model and was just too difficult to implement.
          Hide
          mavik Mavi K added a comment -

          Screen shots that show the missing source links. I needed multiple screen shots to capture the whole Details table. There is some overlap between screen shot 3 and 4.

          One thing to note is that our build system is configured to produce one cppcheck xml file per target and we have multiple targets. The CppCheck jenkins plugin is configured to find all of the cppcheck xml files. Source is shared between targets so this is why there are multiple occurrences of some of the reported issues, although I don't understand why there are multiple occurrences of the same warnings labelled as resolved.

          Show
          mavik Mavi K added a comment - Screen shots that show the missing source links. I needed multiple screen shots to capture the whole Details table. There is some overlap between screen shot 3 and 4. One thing to note is that our build system is configured to produce one cppcheck xml file per target and we have multiple targets. The CppCheck jenkins plugin is configured to find all of the cppcheck xml files. Source is shared between targets so this is why there are multiple occurrences of some of the reported issues, although I don't understand why there are multiple occurrences of the same warnings labelled as resolved.
          Hide
          mavik Mavi K added a comment -

          I modified my job configuration to only read in a single cppcheck xml file. This did not resolve the issue, the links to source are still missing.

          Show
          mavik Mavi K added a comment - I modified my job configuration to only read in a single cppcheck xml file. This did not resolve the issue, the links to source are still missing.
          Hide
          mixalturek Michal Turek added a comment -

          Ok, I understand now. You probably execute Cppcheck from a sub-directory of the workspace, but the plugin expects all paths in the report are relative to the workspace. I have just added "Report in a sub-directory of the workspace (advanced)" section to the plugin wiki, there are two possible solutions to your problem. Please let me know if such help is sufficient for you, I will reject the task in such case.

          Show
          mixalturek Michal Turek added a comment - Ok, I understand now. You probably execute Cppcheck from a sub-directory of the workspace, but the plugin expects all paths in the report are relative to the workspace. I have just added "Report in a sub-directory of the workspace (advanced)" section to the plugin wiki, there are two possible solutions to your problem. Please let me know if such help is sufficient for you, I will reject the task in such case.
          Hide
          mavik Mavi K added a comment -

          Yes, that is correct, I am executing cppcheck form a sub-directory of the workspace. The path replacement work around is satisfactory.

          Show
          mavik Mavi K added a comment - Yes, that is correct, I am executing cppcheck form a sub-directory of the workspace. The path replacement work around is satisfactory.
          Hide
          dantliff David Antliff added a comment -

          Just a note that the wiki, as currently written, does not cope with result entries that contain the optional file0 attribute. I've posted a comment to elaborate here:

          https://wiki.jenkins-ci.org/display/JENKINS/Cppcheck+Plugin?focusedCommentId=100697392#comment-100697392

          Show
          dantliff David Antliff added a comment - Just a note that the wiki, as currently written, does not cope with result entries that contain the optional file0 attribute. I've posted a comment to elaborate here: https://wiki.jenkins-ci.org/display/JENKINS/Cppcheck+Plugin?focusedCommentId=100697392#comment-100697392

            People

            • Assignee:
              mixalturek Michal Turek
              Reporter:
              mavik Mavi K
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: