[cppcheck] Wrong job status set based on new errors treshold

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: cppcheck-plugin
    • None
    • Environment:
      Linux, cppcheck version 1.55, jenkins 1.471, cppcheck plugin 1.9

      Even though CppCheck results page from the analyzis doesn't show new errors (and the sum of errors doesn't change between 2 runs), in the console output of the job we can see that it sets build as unstable as new errors were found.

      [Cppcheck] Setting build status to UNSTABLE since total number of new errors (With all severity values) exceeds the threshold value '1'.
      [Cppcheck] Ending the cppcheck analysis.

      Severity Error (nb/new) : 46/+0
      Severity Warning (nb/new) : 2405/+0
      Severity Style (nb/new) : 1736/+0
      Severity Performance (nb/new) : 1506/+0
      Severity Information (nb/new) : 0/+0
      Severity Unknown (nb/new) : 11/0

            Assignee:
            Gregory Boissinot
            Reporter:
            M S
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: