It does not look like the plug-in depends on analysis core. So I do not see a chance that this will happen.

(There will be a chance that this information can be shown in the not yet released quality-dashboard plug-in. I'll add a comment when the first public release will be available.)

marcosteffan IMHO it is a good idea to use analysis core in cppcheck plugin. It would remove some boilerplate code.

In the next major release (still needs some time) of the warnings plug-in there will be support for cppcheck, see #f22e29d.

drulli Is there any chance I could run a private local build of what's currently release and just add in the cppcheck support or do I need the rest of your work for analysis-core-2.0?  The current released cppcheck plugin is broken for pipelines and there is no sign that a fix for it is coming anytime soon.  The closest I have gotten to something that semi-works with pipelines is this fork: https://github.com/gimmeasandwich/cppcheck-plugin  I'd love to try out the work you've done, but it is based on the latest Jenkins LTS and we're still running 2.89.2, so your updated plugins failed to load for me.  With the significant whitelisting changes in the latest LTS release, we've been waiting a bit to upgrade our production Jenkins build environment.

I downgraded to 2.89.1 now. During development I always use the latest LTS version so I get debugger and Jenkins core sources in sync. The plugins are currently building and available in our CI server:

• Analysis-Core
• Warnings

drulli thank you!  I went ahead and wrote up my own custom parser using the Warnings plugin Jenkins/configure UI and it works great.  We'll switch to your plugin implementation when it comes out officially, but we're covered for now.  Thanks again.

Released in 5.0.0-beta2.