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

Make mapping of PMD levels for the Jenkins PMD plugins configurable

    • Icon: Improvement Improvement
    • Resolution: Incomplete
    • Icon: Major Major
    • warnings-ng-plugin
    • None

      We are using jenkins as part of our internal build process and we recently decided to change the meanings of the PMD levels for our build. To make a long story short, we consider both 4 and 5 to be "low priority". However, it turns out that the Jenkins plugin for collecting PMD information has the mapping "1,2" -> HIGH, "3,4" -> NORMAL, "5" -> LOW hard coded.

      This patch adds new configuration for both the PMD Reporter and the PMD Publisher to make the cutoffs for "HIGH" and "NORMAL" configurable. The defaults are the same as the hard coded values from the current plugin, so upgrading to this change should not change any behavior.

          [JENKINS-52551] Make mapping of PMD levels for the Jenkins PMD plugins configurable

          pretty ping?

          Henning Schmiedehausen added a comment - pretty ping?

          Ulli Hafner added a comment -

          The migration of the PMD parser into the warnings parser is now complete, I think we can integrate such a change into the warnings plugin now.

          Ulli Hafner added a comment - The migration of the PMD parser into the warnings parser is now complete, I think we can integrate such a change into the warnings plugin now.

          Ulli Hafner added a comment -

          If you still want something like that integrated please update your PR to the warnings-ng plugin.

          Ulli Hafner added a comment - If you still want something like that integrated please update your PR to the warnings-ng plugin.

            drulli Ulli Hafner
            hgschmie Henning Schmiedehausen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: