Upgrade Jenkins Warnings plugin to 5.0.1+ or Warnings Next Generation plugin

 The Warnings plugin fails at parsing Git blame:

[WARNINGS] Parsing warnings in console log with parser Maven
<Git Blamer> Using GitBlamer to create author and commit information for all warnings.

 This is due to JENKINS-45572, JENKINS-48302 fixed in Warnings plugin 5.0.0-beta3 (+ analysis-core-plugin).

Warnings plugin 5.0.1 is released but is being replaced by Warnings Next Generation plugin :

This plugin reached end-of-life. All functionality has been integrated into the Warnings Next Generation Plugin.

See Warnings Next Generation plugin (2.1.2) and Static Analysis Model and Parsers Library.
 
https://github.com/jenkinsci/warnings-ng-plugin

The Jenkins Next Generation Warnings plug-in replaces the whole Jenkins Static Analysis Suite. I.e. it makes the following Jenkins plugins obsolete: Android Lint, CheckStyle, Dry, FindBugs, PMD, Warnings, Static Analysis Utilities, Static Analysis Collector Plugins.

https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md

Migration of Pipelines

Pipelines calling the old static analysis steps (e.g., findbugs, checkstyle, etc.) need to call the new recordIssues step now. The same step is used for all static analysis tools, the actual parser is selected by using the step property tools. For more details on the set of available parameters please see section Configuration.

Migration of all other jobs

Freestyle, Matrix or Maven Jobs using the old API used a so called Post Build Action that was provided by each individual plugin. E.g., the FindBugs plugin did provide the post build action "Publish FindBugs analysis results". These old plugin specific actions are not supported anymore, they are now marked with [Deprecated] in the user interface. Now you need to add a new post build step - this step now is called "Record compiler warnings and static analysis results" for all static analysis tools. The selection of the tool is part of the configuration of this post build step. Note: the warnings produced by a post build step using the old API cannot not be read by the new post build actions. I.e., you can't see a combined history of the old and new results - you simply see two unrelated results. There is also no automatic conversion of results stored in the old format available.

Not Yet Supported Features

Some of the existing features of the Warnings plugin are not yet ported to the API. These will be added one by one. Feel free to create an issue or vote for an issue in our [issue tracker](https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20in%20(analysis-model%2C%20analysis-model-api-plugin%2C%20warnings-ng-plugin)).