Expose annotations to the publishChecks step about checks-api-plugin

[uhafner]

BTW: I added an option to render all warnings in the warnings plugin. It is available in the latest release now.

[allout58]

It would be nice to not have to have to rely on the warnings plugin though, if for example I roll my own check or my linter doesn't exist in the warnings plugin (like tslint, which is deprecated)

[uhafner]

As a workaround you can parse such files with the warnings plugin. Then you get the checks for free...

[jammer87]

As a workaround you can parse such files with the warnings plugin. Then you get the checks for free...

I had considered using the warnings plugin, but that only includes new issues as annotations. The annotations disappear if you run the job again and the issue still exists. I want anything in this file to be an annotation, regardless of the results of previous runs.

This plugin is fantastic! The existing functionality has been very beneficial for my team after only a week of using it.

[uhafner]

It might be worth to create a feature request for a toggle in the warnings plugin.