aside of the gui and this lead to ugly command line.
From: 'Christoph Fetzer' via Jenkins Users
Sent: April 3, 2020 3:08 AM
To: Jenkins Users
Subject: Re: CppCheck(XML parsing) with Warning-Next-Generation plugins
For me that looks like an issue of your shell command and not of the
Thanks for the reply.
What I've done is, put this,
echo '
'
inside *execute shell command*, under *Build*. Set Tools *CPPCheck* and
*Build*.
I was waiting that the *
* would produce *new** line* where used. But
they didn't.
On Fri, Apr 3, 2020 at 10:14 AM Ullrich Hafner
wro
> Am 03.04.2020 um 09:07 schrieb 'Christoph Fetzer' via Jenkins Users
> :
>
> For me that looks like an issue of your shell command and not of the plugin.
Exactly!
> [CPPCheck] Skipping execution of recorder since overall result is 'FAILURE'
> Finished: FAILURE
>
The log indicates that my
For me that looks like an issue of your shell command and not of the
plugin. Can you try to store the actual file to your workspace and make the
plugin parse that?
For me the warnings.ng.plugin is just working in conjunction with cppcheck.
What I am doing looks like this:
The cppcheck-call:
cp
Thanks for your reply.
I've used the example xml from the given link, and getting error -
Started by user unknown or anonymous
Running as SYSTEM
Building in workspace
/media/persistent_storage/home/jenkins-warnings/work/workspace/test
[test] $ /bin/sh -xe /tmp/jenkins918250917560153069.sh
+ echo '
> Am 02.04.2020 um 13:06 schrieb Hakan Rafik :
>
> I'm using the next generation plugins to represent the CppCheck warnings and
> errors.
> But the plugins is not parsing Carriage return:
or Line feed:
.
> I've tried to feed the plugins with the given example
> (https://github.com/jenkins
