-
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
[JENKINS-26572] Log Parser incompatible with Jenkins 1.597 (build record change)
Mark Sinclair
created issue -
I found a reference to the code fix for another plugin [5] that needed to change with the format change; the support core. Its latest release on github has the fix.
5.[] ; X.Support Core Plugin - Jenkins - Jenkins Wiki ;; https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin
Latest Release Dec 29, 2014; Jenkins v 1.554.1 Dependencies metrics (version:3.0.0)
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
Pluggin built from source is confirmed to work on Jenkins 1.599 as well.
Cristian Magherusan-Stanciu
added a comment - I'm also impacted by this, and indeed the latest build from source works on 1.599.
Who could officially release a new version of this plugin?
Cristian Magherusan-Stanciu
added a comment - I'm also impacted by this, and indeed the latest build from source works on 1.599.
Who could officially release a new version of this plugin? | Assignee | Original: rgoren [ rgoren ] | New: Manuel Recena Soto [ recena ] |
A new release of this plugin was published few days ago. Can anybody provides feedback?
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Do we know what to fix in the code for this?
Refs;
1.[]Jenkins' Current version is after the ref'd version, ie v 1.598 (2015/01/25) ; X.Changelog | Jenkins CI ;; http://jenkins-ci.org/changelog
2.[]BUG? there are several merged issues but no release since 2010 ; X.Pull Requests · jenkinsci/log-parser-plugin ;; https://github.com/jenkinsci/log-parser-plugin/pulls?q=is%3Apr+is%3Aclosed
3.[]BUG; does not reference Github ; X.Log Parser Plugin - Jenkins - Jenkins Wiki ;; https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin
4.[]Docs about the build record change ; X.
JENKINS-24380Migration - Jenkins - Jenkins Wiki ;; https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration