Hi Craig,

I read all of the comments several times and I think you misunderstood the behavior of the plugin a lot. Actually it's much simpler than you expect.

  • All builds are independent, they share no data.
  • Each build stores only the data that were generated during its run.
  • If you delete a build (or let Jenkins to delete it), all of its data will be lost so the plugin will be unable to use them.
    • Prolong the history to store more builds or to store them for longer time if you need them.
  • Delta is computed dynamically while presenting the results.
    • The currently displayed build and the previous one is used (N and N-1 if exists). It is for example build 50 and 49. If you delete 49 then build 50 and 48 will be used.
    • This can be changed to go deeper in the history and skip builds with no Cppcheck data, e.g. the failed ones.
    • The plugin doesn't consider last stable build, last unstable build, etc. at all.
  • It is surely possible to have zero delta together with non-zero count of new/solved issue. For example if 5 style issues are solved and 5 new ones introduced, the delta will be zero.
    • Unfortunatelly I can't determine if this is the case, the screenshot is incomplete.

Did you consider to use any of these Cppcheck options? I guess they can help you a lot.

       --inline-suppr
           Enable inline suppressions. Use them by placing comments in the form: // cppcheck-suppress memleak before the line to suppress.

       --suppress=<spec>
           Suppress a specific warning. The format of <spec> is: [error id]:[filename]:[line]. The [filename] and [line] are optional. [error
           id] may be * to suppress all warnings (for a specified file or files). [filename] may contain the wildcard characters * or ?.

       --suppressions-list=<file>
           Suppress warnings listed in the file. Each suppression is in the format of <spec> above.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to