one of my another project which I have not enabled any compiler warning is
running PC-Lint by itself. How can i disable the same? :(
Thanks,
Maneesh
On Friday, October 25, 2013 9:53:57 AM UTC-7, Ullrich Hafner wrote:
>
> Line by line if there is no \n in the regular expression... And the
> cons
I have created the bug request :
https://issues.jenkins-ci.org/browse/JENKINS-20277
Please let me know if you require anymore information.
Thanks,
Maneesh
On Friday, October 25, 2013 9:53:57 AM UTC-7, Ullrich Hafner wrote:
>
> Line by line if there is no \n in the regular expression... And the
Line by line if there is no \n in the regular expression... And the console
annotations are automatically removed if I remember correctly.
Seems something is not working in your example. Maybe the best thing is to
debug it... Can you please create a new bug report and attach the console
log and th
Plugin compares Console output against regular expression line by line or
as a whole ?
Thanks,
Maneesh
On Friday, October 25, 2013 2:05:07 AM UTC-7, Daniel Beck wrote:
>
> Do you use the Timestamper plugin on the affected job? Does it work when
> you remove that feature from the job?
>
> On 2
I removed the time stamp from console log, still I get the below
information only
Puppet-Error-Parser: 0 warnings.
- No warnings since build 1.
- New zero warnings highscore: no warnings since yesterday!
Thanks,
Maneesh
On Friday, October 25, 2013 2:05:07 AM UTC-7, Daniel Beck wrote:
Do you use the Timestamper plugin on the affected job? Does it work when you
remove that feature from the job?
On 25.10.2013, at 02:12, Maneesh M P wrote:
> I copied the error and paste to Example log file box and it just works fine
> there. Even in the sample log box, I pasted with or without
I copied the error and paste to Example log file box and it just works fine
there. Even in the sample log box, I pasted with or without time stamp and
my regular expression correctly identified the require fields.
But then why is it not able to detect from console log?
Thanks,
Maneesh
On Thurs
Am 25.10.2013 um 00:42 schrieb Maneesh M P :
> Yes, there is a [WARNINGS] line in the console
>
> 13:36:20 Validating ./modules/xyxz/tests/init.pp ...
> 13:36:20 [WARNINGS] Parsing warnings in console log with parser
> Puppet-Error-Parser
>
I see, i.e. the parser is running. Seems that no ma
And are there messages in the console log from the warnings plugin? They start
with [WARNINGS] in the console log.
And what is shown if you select the page of a build (not the job)?
Ulli
Am 24.10.2013 um 22:11 schrieb Maneesh M P :
> Yes, I did enable the post build option for compiler warnings
Did you enable the collection of compiler warnings in your job?
Am 24.10.2013 um 02:23 schrieb Maneesh M P :
> I did not get that question, there was nothing in the console output. I am
> attaching the images, please take a look
>
> Thanks
> M
>
> On Wednesday, October 23, 2013 2:59:15 PM UTC
But was is the output of the plugin in the console log?
Am Mittwoch, 23. Oktober 2013 schrieb Maneesh M P :
> Yes, there is no side panel link. But the error Trend graph is displayed
> on the right side with no "error" data.
> Just wondering why it is not capturing the error, since my regexp dete
Yes, there is no side panel link. But the error Trend graph is displayed on
the right side with no "error" data.
Just wondering why it is not capturing the error, since my regexp detected
correctly from sample log
On Wednesday, October 23, 2013 8:30:03 AM UTC-7, Ullrich Hafner wrote:
>
> What i
What is in your console log? Is there no side panel link?
Ulli
Am 23.10.2013 um 10:19 schrieb Maneesh M P :
> Ok finally I am able to figure out the regular expression -> ^.*(err:)
> (.*)at(.*\.pp):(\d+)$
> But I had to change the order of mapping script strings the way it is
> assigned, that
Ok finally I am able to figure out the regular expression -> ^.*(err:)
(.*)at(.*\.pp):(\d+)$
But I had to change the order of mapping script strings the way it is
assigned, that shouldnt be a problem i guess.
import hudson.plugins.warnings.parser.Warning
String category = matcher.group(1)
Strin
Yeah, I found that now.. Thank you!! But I am not able to figure out a a
regular expression for below pattern
19:35:11 err: Could not parse for environment production: Syntax error at
'{'; expected '}' at
/home/build/jenkins/workspace/puppet-parser-try/modules/profile/manifests/shard/master.pp:
Isn't there an example in the help of the script and regular
expression text fields?
Ulli
Am Mittwoch, 23. Oktober 2013 schrieb Maneesh M P :
> I would like to add a "error" finding script for our project. I know I can
> add a groovy script under compiler warning global configuration.
> Can anyo
I would like to add a "error" finding script for our project. I know I can
add a groovy script under compiler warning global configuration.
Can anyone give me complete example of the global configuration and a
groovy script ?
Thanks,
M
--
You received this message because you are subscribed to
17 matches
Mail list logo
