• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: log-parser-plugin
• Labels:

  • pipeline

1. fix-showGraphs-with-pipeline.patch

   11 kB

   2024-06-02 17:55

2. 

   parsed-freestyle.png

   357 kB

   2016-02-09 21:18

3. 

   parsed-workflow.png

   365 kB

   2016-02-09 21:18

[JENKINS-32866] Log Parser Plugin does not parse Pipeline console outputs

Jeff Burke created issue - 2016-02-09 21:12

Collapse comment: Jeff Burke added a comment - 2016-02-09 21:19

Jeff Burke added a comment - 2016-02-09 21:19

Screen shots of parse working and not working.

Expand comment: Jeff Burke added a comment - 2016-02-09 21:19

Jeff Burke added a comment - 2016-02-09 21:19 Screen shots of parse working and not working.

Jeff Burke made changes - 2016-02-09 21:19

Attachment		New: parsed-freestyle.png [ 31823 ]
Attachment		New: parsed-workflow.png [ 31824 ]

Jeff Burke made changes - 2016-02-09 21:23

Description

Original: Versions: * Jenkins: 1.644 * Workflow plugins: 1.12 * Log Parser Plugin: 2.0 Issue: I have the following workflow job: {code:java} node {    step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/jenkins-rule-logparser', useProjectRule: false])    echo 'Error: oh no' } {code} and it produces the following console output: {noformat} Started by user anonymous [Workflow] Allocate node : Start Running on master in /var/lib/jenkins/jobs/ntsvc-monitor-dev/workspace [Workflow] node { [Workflow] step [Workflow] echo Error: oh noes [Workflow] } //node [Workflow] Allocate node : End [Workflow] End of Workflow Finished: SUCCESS {noformat} The log parser config (/var/lib/jenkins/jenkins-rule-logparser) is: {noformat} error /Error/ {noformat} The parsed log view shows only: {noformat} Started by user anonymous [Workflow] Allocate node : Start Running on master in /var/lib/jenkins/jobs/ntsvc-monitor-dev/workspace [Workflow] node { {noformat} For a FreeStyle job, the same echo message and log parser rules, results in fully parsed log and the error message is detected/colored red. See attachments for views of parsed log screens.

New: Versions: * Jenkins: 1.644 * Workflow plugins: 1.12 * Log Parser Plugin: 2.0 Issue: I have the following workflow job: {code:java} node {    step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/jenkins-rule-logparser', useProjectRule: false])    echo 'Error: oh no' } {code} and it produces the following console output: {noformat} Started by user anonymous [Workflow] Allocate node : Start Running on master in /var/lib/jenkins/jobs/ntsvc-monitor-dev/workspace [Workflow] node { [Workflow] step [Workflow] echo Error: oh noes [Workflow] } //node [Workflow] Allocate node : End [Workflow] End of Workflow Finished: SUCCESS {noformat} The log parser config (/var/lib/jenkins/jenkins-rule-logparser) is: {noformat} error /Error/ {noformat} The parsed log view shows only: {noformat} Started by user anonymous [Workflow] Allocate node : Start Running on master in /var/lib/jenkins/jobs/ntsvc-monitor-dev/workspace [Workflow] node { {noformat} For a FreeStyle job, the same echo message and log parser rules, results in fully parsed log and the error message is detected/colored red. See attachments for views of parsed log screens. The Jenkins system log does not contain errors for the jobs or the Log Parse plugin... indeed, it contains success messages from the Log Parse plugin.

Manuel Recena Soto made changes - 2016-02-12 16:19

Labels

New: pipeline

Manuel Recena Soto made changes - 2016-02-12 16:19

Summary

Original: Log Parser Plugin does not parse workflow console outputs

New: Log Parser Plugin does not parse Pipeline console outputs

Jesse Glick made changes - 2016-02-18 14:14

Labels

Original: pipeline

New: workflow

Collapse comment: Sorin Sbarnea added a comment - 2016-04-01 19:51

Sorin Sbarnea added a comment - 2016-04-01 19:51

Is this working? It would be quite useful to enable it for pipelines, we are all moving to them now.

Expand comment: Sorin Sbarnea added a comment - 2016-04-01 19:51

Sorin Sbarnea added a comment - 2016-04-01 19:51 Is this working? It would be quite useful to enable it for pipelines, we are all moving to them now.

Collapse comment: Christoph Vogtländer added a comment - 2016-05-12 18:24

Christoph Vogtländer added a comment - 2016-05-12 18:24

IMHO this is the expected behavior. The log parser step only has access to the log to the point where it is called. If called in "finally" (as some sort of post build actions in the pipeline build) this works well:

try {
  node {
       echo 'Error: oh no'
  }
} finally {
  node {
   step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/jenkins-rule-logparser', useProjectRule: false])
  }
}

In order to fail the build add "failBuildOnError: true" (and maybe you need another try/catch block around the log parser step to catch the error and set the build result to FAILURE explicitly (not tested)).

Expand comment: Christoph Vogtländer added a comment - 2016-05-12 18:24

Christoph Vogtländer added a comment - 2016-05-12 18:24 IMHO this is the expected behavior. The log parser step only has access to the log to the point where it is called. If called in "finally" (as some sort of post build actions in the pipeline build) this works well: try { node { echo 'Error: oh no' } } finally { node { step([$class: 'LogParserPublisher' , parsingRulesPath: '/ var /lib/jenkins/jenkins-rule-logparser' , useProjectRule: false ]) } } In order to fail the build add "failBuildOnError: true" (and maybe you need another try/catch block around the log parser step to catch the error and set the build result to FAILURE explicitly (not tested)).

R. Tyler Croy made changes - 2016-07-25 23:52

Workflow

Original: JNJira [ 168563 ]

New: JNJira + In-Review [ 183178 ]

Load more newer events