-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Jenkins 1.597
After upgrade to Jenkins 1.597 the logparser plugin is no longer working. 1.597 includes the major enhancement to how build records are stored, which is possibly a problem for log parser.
The following errors appear in the jenkins output log:
Jan 23, 2015 9:18:21 AM hudson.plugins.logparser.LogParserParser parseLogBody
INFO: LogParserParser: Start parsing : ZZZZZZZZZZZZZZZZZZ
java.lang.NullPointerException
at hudson.plugins.logparser.LogParserParser.parseLogBody(LogParserParser.java:284)
at hudson.plugins.logparser.LogParserParser.parseLog(LogParserParser.java:114)
at hudson.plugins.logparser.LogParserPublisher.perform(LogParserPublisher.java:54)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1743)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Jan 23, 2015 9:18:21 AM hudson.plugins.logparser.LogParserPublisher perform
SEVERE: null
I pulled the plugin in its current state from the "Available Plugins Menu", and experienced a bug along these lines.
I pulled the source, compiled and loaded my own version on a personal server... which worked out of the box. I even parsed output from a WebStart slave. I ran into an access violation when I tried to use an SSH slave, so I'm not certain where that leaves this bug.
It appears to have been worked on... but I don't know when we'll see a release.
Confirmed on 1.598