Screen shots of parse working and not working.

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

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)).

so, assuming the file of rules is {{/var/lib/jenkins/ParsingRuleFiles/Generic_Verify }}than to fail a build, it should be something like : 

 finally {
        node('<same agent you run on >') {
            try {
                     step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/ParsingRuleFiles/Generic_Verify', useProjectRule: false, *failBuildOnError: true, unstableOnWarning: true*])
         } catch(all) {
                      print "ERROR: LogParserPublisher failed: \n" +all
         }
       }//node
}//finally

tested - and working , me very happy

How could I get to work if I have multiple stages, like the following and I want it to parse everything

pipeline {
    agent { label 'testmachine'}
    stages {
        stage('Level 1'){
            steps {
                      bat '''
                          call "%VS120COMNTOOLS%\\vsvars32.bat"
                          devenv testlevel1.sln /build "Profile|x64"'''
            }
        }
        stage('Level 2'){
            steps {
                     bat '''
                         call "%VS120COMNTOOLS%\\vsvars32.bat" 
                         devenv testlevel2.sln /build "Profile|x64"'''
            }
       }
   }
}

The given solution works for all stages, you just need to set the parser as the last stage.

Can I ask if this is tailored for Declarative Pipelines?

You can of course

I don't see why it wouldn't work, just try.

Hi all!
In my pipeline i have problem. Job failed in this stage(log-parser)

pipeline {
agent

triggers

environment

..........

stage('Log-parser') {
steps {
logparser([$class: 'LogParserPublisher',
parsingRulesPath: '/var/lib/jenkins/minimal-rules',
useProjectRule: false,
failBuildOnError: true,
unstableOnWarning: false,
Logparsergraphs: true ])

error:
java.lang.NoSuchMethodError: No such DSL method 'logparser' found among steps ....... and more string

Well what about the end of the stage?

} catch(all)

}
}

Would be easier to help you if you put the all code in (at least the complete stage).

Hi! Thx for answer. her is cod

pipeline

triggers

environment

stages{
stage('Checkout') {
steps

}
stage('Deploy') {
parallel {
stage('Syntax check') {
steps {
ansiColor('gnome-terminal')

}
}
stage('Check provision for virtual machines') {
steps {
ansiColor('gnome-terminal')

}
}
}
}
stage('Log-parser') {
steps

}
}

Well I'm using 2 different ways for pipeline code:

in Jenkins job as last stage:

stage("Parser") {
node('master') {
try 

catch(all)

}
}

in Jenkinsfile:
@Library('pipelib@master')
import […]

timestamps {
try

finally {
node

}
}

The only difference with your code is that your parsing step is missing
try {} / catch(all) {}
or try {} / finally {}

Also not sure how Ansible affects it as I'm not using it.

thx. I published a new release with your fixes: https://github.com/jenkinsci/log-parser-plugin/releases/tag/v2.3.4

mreinhardt  Thank you very much for this fast response.

BTW: As far as I can see this also solved JENKINS-35265