Sorry for re-opening this bug but adding support for the Workflow without documenting it on the plugin homepage seems like a good reasons to consider this feature not fully implemented.

I would not mind editing the the https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin page and adding the information related to Workflow usage but I don't know yet which is this information.

Once I have a simple pipeline code example I would add it to the wiki.

I agree with ssbarnea above.
An example would help a great deal for beginners.

Thanks in advance.

Please, be nice and document how to use it with pipeline on the page of the plug-in.

Thanks a lot.

Well LogParserPublisher was made into a SimpleBuildStep. Thus it should automatically appear as an option under step in your Pipeline Syntax page. No further documentation should be needed I suppose.

There seems to be an error in the snippet generated for logParser in the Pipeline Syntax page. I generated the snippet

logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false

which gives me the error

WorkflowScript: 73: Missing required parameter: "projectRulePath" @ line 73, column 13.
               logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false
               ^

Adding

, projectRulePath: ''

to the end of the snippet fixes this error.

In addition, why is the path in the logParser call instead of the name of the rule, as specified in a none-pipeline job or in the snippet generator itself? This will be hell for me if the drive location of the global log parser rule ever changes...

Thanks.

PS: I know it's a lot of work to keep this stuff up-to-date, but IMHO, further documentation is needed (not just for this plugin). E.g. there is an option showGraphs (https://jenkins.io/doc/pipeline/steps/log-parser/) with no explanation. I tried it, hoping it might give me maybe parsing on step level, and found no effect.