Log Parser Plugin: Configuration
Andreas Schilling
has anyone successfuly used the log parser plugin? it's definitely something we'd like to use but no matter where we put the config file, the plugin is unable to find it. I also checked all logs to find out on which path it is searched, but I also wasn't able to find any hints. before I invest several hours into finding a location where to put the files, maybe someone who had success on that can drop me a hint? :-)
kind 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
--------------------------------------------------------------------
www.twt-gmbh.de
--------------------------------------------------------------------
Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (stv.)
Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778
Umsatzsteuer: ID-Nr.: DE147841145
--------------------------------------------------------------------
Simon Wiest
I haven't used the plugin myself yet. But as far as I understand, the
log parser plugin
(http://wiki.hudson-ci.org/display/HUDSON/Log+Parser+Plugin) does not
parse a specific text file that is created during your build. Instead,
it scans the console output of your build.
You'll have to make sure, that the required "action words" are printed
to the standard output during the build and thus show up in the console
log, e.g. using echo commands.
Cheers,
Simon.
--
Andreas Schilling (31.01.2011 12:52):
Andreas Schilling
yes, the plugin just parses the console output. however, you need to supply it a rules-file that contains the regular expressions it uses to parse the log. this needs to be put somewhere and I do not understand where. it's nowhere documented. some people claim it must be the hudson home, some say it's the windows system directory but none of the locations anyone suggested works for me.
hope that clarifies my problem :)
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
--------------------------------------------------------------------
Denis Silakov
How do you setup the plugin? We simply set absolute paths to files with parsing rules at the Global Configuration (in the similar way as one can see at the plugin page - http://wiki.hudson-ci.org/display/HUDSON/Log+Parser+Plugin), and we have never faced any problems with them. (To be sure, these files should be readable for hudson user).
Petriconi, Felix
Andreas,
I have a file with a content like this
ok /not really/
error /error (LNK|C)[\d*]/
error /general error/
warning /warning C[\d*]/
warning /warning LNK(?!(4199)|(4099))/
info /not really/
error /ERROR :/
error /FAILED:/
google test error /\[ FAILED \]/
in ${HUDSON_HOME}\ParsingRules\UpdateBuild and I used in the system configuration dialog an absolute path like E:/Hudson_Home/ParsingRules/UpdateBuild.
That works for me.
Regards, Felix
Development Manager
MeVis BreastCare Solutions GmbH & Co. KG
A MeVis Medical Solutions company
Universitaetsallee 29
28359 Bremen
Germany
Phone: +49 (0)421 33074-(9)20
Fax: +49 (0)421 33074-50
E-mail: felix.p...@mevis.de
Website: www.mevis.de
Trade Registry: Bremen HRA 25204 HB
VAT ID: DE262661277
Executive Board:
Carl J.G. Evertsz, Ph.D., Robert Hannemann, Ph. D.
MeVis BreastCare Solutions Verwaltungs-GmbH
Simon Wiest
ah, now I understand... ;O)
Did you see the configuration setting in "Manage Hudson->Configure
System->Console Output Parsing"? I just ran a quick test with an
absolute pathname to a rule file there and it worked without any trouble.
Do you get any error messages?
Cheers,
Simon.
--
Andreas Schilling (31.01.2011 13:17):
Andreas Schilling
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
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.
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
--------------------------------------------------------------------
Simon Wiest
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>
John Borghi
The plugin currently references the file from the master. I recommend using an absolute path, as it is relative to the process that starts Hudson otherwise. The next version will also allow input via a text area as there are a few requests for this.
Let me know if you have other questions.
John
Andreas Schilling
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
--------------------------------------------------------------------
--------------------------------------------------------------------
Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (stv.)
Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778
Umsatzsteuer: ID-Nr.: DE147841145
--------------------------------------------------------------------
