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

Ability to configure thresholds for each Warnings parser used

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • warnings-plugin
    • Jenkins 1.532.3 , Warnings plugin 4.40
    • 5.0.0-beta2

      Currently when adding more than one Warnings parser type to a Job you can only add the Scan for Warnings task once and therefore you can only configure the threshold settings only once.
      It would be very useful to either be able to configure the thresholds per Warnings parser type or if you could add the Scan for Warnings task more than once per Job in the Post Build steps.

      For example, warnings from MSBuilds tasks have a higher meaning to us than Robocopy warnings so being able to set those thresholds differently would be very useful.

          [JENKINS-22874] Ability to configure thresholds for each Warnings parser used

          Arno Moonen added a comment -

          This is something I'm also looking for. Has anyone worked on this yet?
          Also, which plugins would need to change for this to happen, just the warnings-plugin or also the analysis-core plugin?

          Arno Moonen added a comment - This is something I'm also looking for. Has anyone worked on this yet? Also, which plugins would need to change for this to happen, just the warnings-plugin or also the analysis-core plugin?

          Ulli Hafner added a comment -

          Nobody is working on this. It can be implemented in the warnings plugin alone or in analysis-core and the warnings plugin. In the latter case it would make sense to rather implement JENKINS-14185 und reuse these concepts.

          I already started an implementation some years ago: https://github.com/jenkinsci/analysis-core-plugin/tree/JENKINS-14185. However, I never finished it. Are you interested in providing an implementation? Then I can bring the branch up to date....

          Ulli Hafner added a comment - Nobody is working on this. It can be implemented in the warnings plugin alone or in analysis-core and the warnings plugin. In the latter case it would make sense to rather implement JENKINS-14185 und reuse these concepts. I already started an implementation some years ago: https://github.com/jenkinsci/analysis-core-plugin/tree/JENKINS-14185 . However, I never finished it. Are you interested in providing an implementation? Then I can bring the branch up to date....

          Ulli Hafner added a comment -

          I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page. Can you please read it carefully and comment or change it accordingly?

          Ulli Hafner added a comment - I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page . Can you please read it carefully and comment or change it accordingly?

          Ulli Hafner added a comment -

          Released in 5.0.0-beta2.

          Ulli Hafner added a comment - Released in 5.0.0-beta2.

            drulli Ulli Hafner
            jstarbird Jon Starbird
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: