When using the Record compiler warnings and static analysis results post-build action, we want to be able to set the Quality Gate Thresholds per configured tool.

In the past we had separate post-build actions for CPD and PC-Lint.
The post build action from the DRY plugin for CPD was configured in such a way that it never failed the build (only generated the report).
The post build action from the Warnings plugin for PC-Lint was configured so that the total number of warnings may not increase (which is also missing in the NG plugin at the moment, see JENKINS-52098).

Currently migrating from both DRY and Warnings to Warnings Next Generation does not seem possible for us, because we can only set the Quality Gate Thresholds for all the configured tools in the Post-build action.