Make mapping of PMD levels for the Jenkins PMD plugins configurable

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Ulli Hafner
            Reporter:
            Henning Schmiedehausen
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: