Hi Andreas, Which solution worked for you? Did you have to restart the Hudson service? Or, just disable and reenable "Console output (build log) parsing"? I'm having the same issue, and I've tried the latter but to no avail. Still getting the same error. I would rather not have to restart the server if I don't have to.
Thanks, Jay On Tuesday, February 1, 2011 2:40:47 AM UTC-8, Andreas Schilling wrote: > > Hi Simon and all the others! > > Thanks for the help, now it finally works :) > > Regards, > > Andreas Schilling > Information Engineering > ------------------------------------------------------------------- > Dipl. Inf. Andreas Schilling > Software Architect, Information Engineering > > TWT GmbH > Science & Innovation > Bernhäuser Str. 40 - 42 > 73765 Neuhausen > > Tel: +49 - 7158 - 17 15 - 23 > E-Mail: andreas....@twt-gmbh.de <javascript:> > -------------------------------------------------------------------- > www.twt-gmbh.de > -------------------------------------------------------------------- > Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (stv.) > Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778 > Umsatzsteuer: ID-Nr.: DE147841145 > -------------------------------------------------------------------- > > > > Von: Simon Wiest <simon...@web.de <javascript:>> > An: hudson...@googlegroups.com <javascript:> > Datum: 31.01.2011 15:57 > Betreff: Re: Log Parser Plugin: Configuration > Gesendet von: hudson...@googlegroups.com <javascript:> > ------------------------------ > > > > Hi Andreas, > > I think, I've found the cause: > > Choosing a rule set in the project configuration *copies* the current > path as defined in the global configuration to the projects > configuration (as opposed to referencing it). Any changes that you'll do > later on in the global configuration will therefore not be reflected on > a project level ;o(. > > Workaround: > > 1.) Make sure, the file path in the global configuration is o.k. > 2.) Then disable open "Console output (build log) parsing" > in project configuration. Save. > 3.) Enable "Console output (build log) parsing" again. > Pick desired rule set definition. Save. > 4.) Build... > > Does this solve your problem? And could you open a bug ticket for this > in the Hudson JIRA anyway ;o)? > > Cheers, > Simon. > -- > Andreas Schilling (31.01.2011 14:07): > > hi! > > > > yes, I do get an error: > > log-parser plugin ERROR: Cannot parse log: Can't read parsing rules > > file:D:/Programme/Hudson/default_output_parsing > > <file://D:/Programme/Hudson/default_output_parsing> > > > > in the configuration for the plugin I do set the path exactly like this: > > D:\Programme\Hudson\default_output_parsing > > > > the file is there and permissions should also be correct. > > also, it seems a change on the path to the rules file is only recognized > > when you completely restart the hudson service. but that's another issue. > > > > kind regards, > > > > Andreas Schilling > > !DSPAM:590,4d46cde2255938362916074! > > > -- 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.
