As soon as the pipeline measures more issues because a new tool is detected used by the git repository then it is quite possible that the defined quality gate will always fail. This is a gap in the plugin. It is not possible to define tool-specific quality gates.Please make
Please make the steps {{recordIssues}} and {{publishIssues}} configurable in the way that Jenkins will display one aggregation trend chart and no scanner-specific trend chart on the Jenkins job status page independent how often the steps are configured/called.