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

More data from REST API

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I am requesting that more data be available from the cppcheck rest api.
      Example URL:
      http://<jenkins_server>/job/<job_name>/<build_number>/cppcheckResult/api/xml

      It currently gives 7 summary pieces of data:
      numberErrorSeverity
      numberInformationSeverity
      numberNoCategorySeverity
      numberPerformanceSeverity
      numberStyleSeverity
      numberTotal
      numberWarningSeverity

      I am asking for the detailed information as well. Please provide the entire table of detailed information as viewed from the Cppcheck Result page.

        Attachments

          Activity

          Hide
          mixalturek Michal Turek added a comment -

          Hi Robert, can you describe your use case, please? Did you consider to store the Cppcheck report to the build artifacts and access this file instead? It is a XML file suitable for parsing, it contains even more information than the plugin itself and it can be simply downloaded from a defined URL.

          Show
          mixalturek Michal Turek added a comment - Hi Robert, can you describe your use case, please? Did you consider to store the Cppcheck report to the build artifacts and access this file instead? It is a XML file suitable for parsing, it contains even more information than the plugin itself and it can be simply downloaded from a defined URL.
          Hide
          robs RobS added a comment -

          Well I suppose you have a good point. However it would be more convenient for me when creating jobs not to have to do an additional step of keeping a build artifact around. But that's probably not worth the coding effort to keep data around for the REST api or whatever must happen. So thanks for pointing this out. You can close this issue.

          Show
          robs RobS added a comment - Well I suppose you have a good point. However it would be more convenient for me when creating jobs not to have to do an additional step of keeping a build artifact around. But that's probably not worth the coding effort to keep data around for the REST api or whatever must happen. So thanks for pointing this out. You can close this issue.
          Hide
          mixalturek Michal Turek added a comment -

          Rejected, can be fully solved using a simple workaround.

          Show
          mixalturek Michal Turek added a comment - Rejected, can be fully solved using a simple workaround.

            People

            • Assignee:
              mixalturek Michal Turek
              Reporter:
              robs RobS
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: