Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32866

Log Parser Plugin does not parse Pipeline console outputs

XMLWordPrintable

      Versions:

      • Jenkins: 1.644
      • Workflow plugins: 1.12
      • Log Parser Plugin: 2.0

      Issue:
      I have the following workflow job:

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

      and it produces the following console output:

      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
      

      The log parser config (/var/lib/jenkins/jenkins-rule-logparser) is:

      error /Error/
      

      The parsed log view shows only:

      Started by user anonymous
      [Workflow] Allocate node : Start
      Running on master in /var/lib/jenkins/jobs/ntsvc-monitor-dev/workspace
      [Workflow] node {
      

      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.

        1. fix-showGraphs-with-pipeline.patch
          11 kB
          Marc
        2. parsed-freestyle.png
          357 kB
          Jeff Burke
        3. parsed-workflow.png
          365 kB
          Jeff Burke

            mreinhardt Martin Reinhardt
            potatopankakes Jeff Burke
            Votes:
            13 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: