This is a pitfall I struggled with yesterday myself.
The plugin is not actually broken, it simply lacks of documentation at this point: In contrast to the old 'warnings' plugin, the parameters are shifted by one which I think is kind of more intuitive as the threshold now defines the minimum amount of issues that will fail the build.
So if you intend to enforce the warning-free policy, your threshold value must be 1 (not 0 as with the old plugin).
However, what I discovered is that if you set values to 0, the plugin behaves as if the parameter has not been set and the parameter will be skipped when calculating the quality gate.
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.