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 detected > correctly from sample log > > On Wednesday, October 23, 2013 8:30:03 AM UTC-7, Ullrich Hafner wrote: >> >> What is in your console log? Is there no side panel link? >> >> Ulli >> >> Am 23.10.2013 um 10:19 schrieb Maneesh M P <[email protected]>: >> >> 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) >> String message = matcher.group(2) >> String fileName = matcher.group(3) >> String lineNumber = matcher.group(4) >> >> >> return new Warning(fileName, Integer.parseInt(lineNumber), "Dynamic >> Parser", category, message); >> >> Now I configure the job with Name I gave for parser, But i don't see any >> "Link name" displayed in the build page :( >> any clue? >> >> Thanks, >> M >> >> On Tuesday, October 22, 2013 11:32:14 PM UTC-7, Maneesh M P wrote: >>> >>> 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:5 >>> 19:35:11 err: Try 'puppet help parser validate' for usage >>> >>> Whatever I write, I get this error "The regular expression does not >>> match the example text." >>> >>> Thanks, >>> M >>> >>> On Tuesday, October 22, 2013 10:31:49 PM UTC-7, Ullrich Hafner wrote: >>>> >>>> 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 anyone give me complete example of the global configuration and a >>>>> groovy script ? >>>>> >>>>> Thanks, >>>>> M >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to jenkinsci-users+unsubscribe@**googlegroups.com. >>>>> For more options, visit >>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-use...@**googlegroups.com. >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:_e({}, > 'cvml', 'jenkinsci-users%[email protected]');>. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
