-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins: 2.249.2
Log Parser Plugin: 2.1
One job is not triggering Console Log Parser, while other jobs are working fine.
Not seeing the line below in the console output, which tells me it's not being triggered.
Build step 'Console output (build log) parsing' changed build result to FAILURE
Working job config.xml
<hudson.plugins.logparser.LogParserPublisher>
<unstableOnWarning>true</unstableOnWarning>
<failBuildOnError>true</failBuildOnError>
<showGraphs>false</showGraphs>
<parsingRulesPath>/opt/jenkins/crs/build_parser_rules/jenkins_build.parser</parsingRulesPath>
<useProjectRule>false</useProjectRule>
</hudson.plugins.logparser.LogParserPublisher>
Not working job config.xml
<hudson.plugins.logparser.LogParserPublisher plugin="log-parser@2.1">
<unstableOnWarning>true</unstableOnWarning>
<failBuildOnError>true</failBuildOnError>
<showGraphs>false</showGraphs>
<parsingRulesPath>/opt/jenkins/crs/build_parser_rules/jenkins_build.parser</parsingRulesPath>
<useProjectRule>false</useProjectRule>
</hudson.plugins.logparser.LogParserPublisher>
The only difference I found is that the plugin version is specified in the second config. I tried removing it and reloading the jobs but this doesn't seem to have resolved it.
Hi mreinhardt - I recorded some logs for the hudson.plugins.logparser class and found the below.
Job that parses successfully (Aborts job as expected)
Nov 06, 2020 8:40:33 AM INFO hudson.plugins.logparser.LogParserParser parseLogBody
LogParserParser: Start parsing : Job2_64
Nov 06, 2020 8:40:33 AM INFO hudson.plugins.logparser.LogParserStatusComputer computeStatusMatches
Local temp file:/tmp/log-parser_Job2_64
Nov 06, 2020 8:40:33 AM INFO hudson.plugins.logparser.LogParserReader readLogPart
Start reading log part 0 in thread #0
Nov 06, 2020 8:40:33 AM INFO hudson.plugins.logparser.LogParserReader readLogPart
Done reading log part 0
Nov 06, 2020 8:40:33 AM INFO hudson.plugins.logparser.LogParserThread getLineStatuses
LogParserThread: Start parsing log part 0
Nov 06, 2020 8:40:33 AM INFO hudson.plugins.logparser.LogParserThread getLineStatuses
LogParserThread: Done parsing log part 0
Nov 06, 2020 8:40:33 AM INFO hudson.plugins.logparser.LogParserParser parseLogBody
LogParserParser: Parsing took 0 minutes (0) seconds.
Job where parsing fails (Fails job instead of aborting)
Nov 06, 2020 8:50:33 AM INFO hudson.plugins.logparser.LogParserParser parseLogBody
LogParserParser: Start parsing : Job1_12
Nov 06, 2020 8:50:33 AM INFO hudson.plugins.logparser.LogParserParser parseLogBody
LogParserParser: Parsing took 0 minutes (0) seconds.
It looks like computeStatusMatches, readLogPart and getLineStatuses are not called after parseLogBody in the failed job. I'll see if I can try providing any more information - let me know what else I can provide to help troubleshoot. Thanks