How to use Email-ext and Log Parser (with jelly script) pluins in Hudson/Jenkins? -
how use log parser email-ext plugin parsed console output via e-mail?
i use ${jelly_script,template="html"} formatted message.
after installing , configuring log parser plugin, still getting emails not parsed console output.
console parser plugin creates separate html files can later displayed via link on build status page. has nothing email-ext plugin (at least not directly). there couple of options see it:
- forget log parser plugin in e-mails. format output in template (for more heavy-duty formatting can use groovy script option of emailext plugin).
- provide summary in e-mail , include link parsed console output. it's @
http://<jenkins_server>/job/<job-name>/<build-num>/parsed_console.
as aside:
log parser plugin great time-saver when have huge logs.
in general experience shows build e-mails more of nuisance of help: either there many people ignore them, or few of real service. reason managers love them, while developers hate them. i've spent week creating super-duper report emailext , groovy - in end nobody looks @ it. e-mails find helpful sent committers broke build. in short, make sure not waste time on looks sexy, in end worthless.
Comments
Post a Comment