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 25.10.2013, at 02:12, Maneesh M P <manees...@gmail.com <javascript:>> > 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 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 Thursday, October 24, 2013 3:57:54 PM UTC-7, Ullrich Hafner wrote: > > > > Am 25.10.2013 um 00:42 schrieb Maneesh M P <manees...@gmail.com>: > > > >> 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 match is found. Did you > paste the conflicting line of console log into the example text box? Maybe > the expression is not exactly the same (note the timestamp is automatically > removed!)… > > > > > >> Sorry I could not understand "what is shown n the select page of a > build", which page are you referring to ? > > > > > > You only show the overall job status. You can navigate to the results of > each build, there you will see a summary of the warnings plugin > > See right image in > https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-summary > > > > > > >> I am attaching the three screenshot of different pages > >> > >> Thanks, > >> Maneesh > >> > >> On Thursday, October 24, 2013 1:30:53 PM UTC-7, Ullrich Hafner wrote: > >> 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 <manees...@gmail.com>: > >> > >>> Yes, I did enable the post build option for compiler warnings. Please > see the attached images. > >>> > >>> On Thursday, October 24, 2013 11:19:59 AM UTC-7, Ullrich Hafner wrote: > >>> Did you enable the collection of compiler warnings in your job? > >>> > >>> Am 24.10.2013 um 02:23 schrieb Maneesh M P <manees...@gmail.com>: > >>> > >>>> 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-7, Ullrich Hafner > wrote: > >>>> 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 <manees...@gmail.com>: > >>>> > >>>>> 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-use...@googlegroups.com <javascript:>. > >>>>> 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 jenkinsci-use...@googlegroups.com. > >>>>> 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 jenkinsci-use...@googlegroups.com <javascript:>. > >>>> 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 jenkinsci-use...@googlegroups.com. > >>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>> <error-parse.JPG><console.png> > >>> > >>> > >>> -- > >>> 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. > >>> > <puppet-parser-global-configuration.JPG><puppet-parser-job-configuration.JPG> > > >> > >> > >> -- > >> 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. > >> <page1.jpg><page2.jpg><page3.JPG> > > > > > > -- > > 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 <javascript:>. > > 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
