• 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

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

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

Workflow

Original: JNJira [ 168563 ]

New: JNJira + In-Review [ 183178 ]

Andrew Bayer made changes - 2016-08-29 17:25

Labels

Original: workflow

New: pipeline workflow

Andrew Bayer made changes - 2016-08-29 17:26

Labels

Original: pipeline workflow

New: pipeline

Prince Raj Kumar made changes - 2018-04-30 06:53

Priority

Original: Minor [ 4 ]

New: Major [ 3 ]

Martin Reinhardt made changes - 2019-07-04 02:50

Assignee

Original: Manuel Recena Soto [ recena ]

New: Martin Reinhardt [ mreinhardt ]

Load more newer history items