• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • warnings-ng-plugin
    • None
    • 5.0.0 (analysis-model and warnings-ng)

      I tried to set the health report level to

       

      healthy: 0 unhealthy: 1

      this  causes an error, that both healthy and unhealthy should be set.

      (guess : code needs to discriminiate between NULL/unset and 0/zero.)

          [JENKINS-55293] Unable to set healthy levels to 0

          Ulli Hafner added a comment -

          0 is an invalid value. The first valid value is 1 because I compare with < and >. I think I need to improve the error message.

          Ulli Hafner added a comment - 0 is an invalid value. The first valid value is 1 because I compare with < and >. I think I need to improve the error message.

          When setting it to healthy=1, I get 100% health when having exactly one issue. If "<" is used, I don't understand why I get 100%

          unhealthy=5 in this environment

          Christian Treczoks added a comment - When setting it to healthy=1, I get 100% health when having exactly one issue. If "<" is used, I don't understand why I get 100% unhealthy=5 in this environment

          Ulli Hafner added a comment - - edited

          christiantreczoks your attachment is broken. What values did you specify for healthy and unhealthy?

          Ulli Hafner added a comment - - edited christiantreczoks your attachment is broken. What values did you specify for healthy and unhealthy ?

          my settings: healthy: 1, minimumSeverity: 'NORMAL', unhealthy: 5

          and I get the following result:

          My expectation is: 80% for "Unused Functions"

          P.S.: I use the groovy based custom parser and the latest Warning-NG-Version (4.0.0)

          Christian Treczoks added a comment - my settings: healthy: 1, minimumSeverity: 'NORMAL', unhealthy: 5 and I get the following result: My expectation is: 80% for "Unused Functions" P.S.: I use the groovy based custom parser and the latest Warning-NG-Version (4.0.0)

          Works perfectly now with Warning-NG 5.0.0

          I wouldn't expect a sun, but that's not the responsibility of Warnings-NG-Plugin

          Christian Treczoks added a comment - Works perfectly now with Warning-NG 5.0.0 I wouldn't expect a sun, but that's not the responsibility of Warnings-NG-Plugin

          tsondergaard added a comment -

          drulli , I don't understand why this issue is resolved as fixed. It still does not appear to be possible to configure this plugin so anything above 0 warnings as 0% healthy. This seems like it should be the most desirable configuration to use, ie tolerate no warnings.

          tsondergaard added a comment - drulli , I don't understand why this issue is resolved as fixed. It still does not appear to be possible to configure this plugin so anything above 0 warnings as 0% healthy. This seems like it should be the most desirable configuration to use, ie tolerate no warnings.

            drulli Ulli Hafner
            pedersen Björn Pedersen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: