[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Martin Reinhardt assigned an issue to Martin Reinhardt Jenkins / JENKINS-32866 Log Parser Plugin does not parse Pipeline console outputs Change By: Martin Reinhardt Assignee: Manuel Recena Soto Martin Reinhardt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168062.1455052339000.1502.1562208692806%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
Pierre Marton edited a comment on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
Well I'm using 2 differents different ways for pipeline code:in Jenkins job as last stage:stage("Parser") { node('master') { {color:#FF} try { {color} step([$class: 'LogParserPublisher', parsingRulesPath: 'YOUR_PARSING_FILE', useProjectRule: false, failBuildOnError: true, unstableOnWarning: true]) {color:#FF } } catch(all) {{color} { color:#FF} print "ERROR: LogParserPublisher failed: \n" +all {color } {color:#FF} }{color} }}in Jenkinsfile:@Library('pipelib@master')import […]timestamps { {color:#FF} try { // For finally LogParserPublisher {color} […] } {color:#FF}} finally { {color} node {step([$class: 'LogParserPublisher', parsingRulesPath: 'YOUR_PARSING_FILE', useProjectRule: false])} {color:#FF } }{color} } I've put in red the 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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
Pierre Marton commented on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
Well I'm using 2 differents ways for pipeline code: in Jenkins job as last stage: stage("Parser") { node('master') { try { step([$class: 'LogParserPublisher', parsingRulesPath: 'YOUR_PARSING_FILE', useProjectRule: false, failBuildOnError: true, unstableOnWarning: true]) {color:#FF}} catch(all) {{color} print "ERROR: LogParserPublisher failed: \n" +all } } } in Jenkinsfile: @Library('pipelib@master') import […] timestamps { try { // For finally LogParserPublisher […] {color:#FF}} finally {{color} node { step([$class: 'LogParserPublisher', parsingRulesPath: 'YOUR_PARSING_FILE', useProjectRule: false]) } {color:#FF}} } I've put in red the only difference with your code. Also not sure how Ansible affects it as I'm not using it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
Martin Dan commented on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
Hi! Thx for answer. her is cod pipeline { agent \{ label 'master'} triggers { pollSCM('* * * * *') } environment { ANSIBLE_CONFIG = "Jenkins-LTS/ansible.cfg" } stages{ stage('Checkout') { steps { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'Jenkins-LTS'], [$class: 'WipeWorkspace']], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'fd864bf0-5e33-4cf1-a130-67ac2c22bf17', url: 'https://github.com/MRDO5/jenkins-lts.git']]]) } } stage('Deploy') { parallel { stage('Syntax check') { steps { ansiColor('gnome-terminal') { ansiblePlaybook become: true, colorized: true, credentialsId: '7980492c-7fa3-41b6-9c8e-b44d3f7ce236', extras: '--syntax-check' , inventory: 'Jenkins-LTS/inventory', playbook: 'Jenkins-LTS/main.yml' } } } stage('Check provision for virtual machines') { steps { ansiColor('gnome-terminal') { ansiblePlaybook become: true, colorized: true, credentialsId: '7980492c-7fa3-41b6-9c8e-b44d3f7ce236', installation: 'ansible', inventory: 'Jenkins-LTS/inventory', playbook: 'Jenkins-LTS/main.yml' } } } } } stage('Log-parser') { steps { logparser([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/minimal-rules', useProjectRule: false, failBuildOnError: true, unstableOnWarning: false, Logparsergraphs: true ]) } } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
Pierre Marton commented on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
Well what about the end of the stage? } catch(all) { print "ERROR: LogParserPublisher failed: \n" +all } } } Would be easier to help you if you put the all code in (at least the complete stage).
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
Martin Dan commented on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
Hi all! In my pipeline i have problem. Job failed in this stage(log-parser) pipeline { agent { label 'master' } triggers { pollSCM('* * * * *') } environment { ANSIBLE_CONFIG = "Jenkins-LTS/ansible.cfg" } .. 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
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Pierre Marton commented on JENKINS-32866 Re: Log Parser Plugin does not parse Pipeline console outputs You can of course I don't see why it wouldn't work, just try. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Jake D commented on JENKINS-32866 Re: Log Parser Plugin does not parse Pipeline console outputs Can I ask if this is tailored for Declarative Pipelines? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Pierre Marton commented on JENKINS-32866 Re: Log Parser Plugin does not parse Pipeline console outputs The given solution works for all stages, you just need to set the parser as the last stage. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
Lawrence Dubé edited a comment on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
How could I get to work if I have multiple stages, like the following and I want it to parse everything{code:java}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" ''' } }} } {code}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
Lawrence Dubé commented on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
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"
'''
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
danniel hughes edited a comment on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
so, assuming the file of rules is {{{color:#00875a}/var/lib/jenkins/ParsingRuleFiles/Generic_Verify {color}}}than to fail a build, it should be something like : {quote}{{ finally {}} {{ node('__') {}} {{ try {}} {{ step([$class: '{color:#00875a}LogParserPublisher{color}', parsingRulesPath: '{color:#00875a}/var/lib/jenkins/ParsingRuleFiles/Generic_Verify{color}', useProjectRule: false, *{color:#403294}failBuildOnError{color}: {color:#de350b}true{color}, {color:#403294}unstableOnWarning{color}: {color:#de350b}true{color}*])}} {{ } catch(all) {}} \{{ print "ERROR: LogParserPublisher failed: \n" +all }} {{ }}} {{ }//node}} {{}//finally}}{quote}{quote}{{tested - and working , me very happy :)}}{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
danniel hughes edited a comment on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
so, assuming the file of rules is {{{color:#00875a}/var/lib/jenkins/ParsingRuleFiles/Generic_Verify {color}}}than to fail a build, it should be something like : {quote}{{ finally {}} {{ node('__') {}} {{ try {}} {{ step([$class: '{color:#00875a}LogParserPublisher{color}', parsingRulesPath: '{color:#00875a}/var/lib/jenkins/ParsingRuleFiles/Generic_Verify{color}', useProjectRule: false, *{color:#403294}failBuildOnError{color}: {color:#de350b}true{color}, {color:#403294}unstableOnWarning{color}: {color:#de350b}true{color}*])}} {{ } catch(all) {}} \ {{ print " -E- ERROR: LogParserPublisher failed: \n" +all }} {{ }}} {{ }//node}} {{}//finally}}{quote}{quote}{{tested - and working , me very happy :)}}{quote}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
danniel hughes edited a comment on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
so, assuming the file of rules is {{{color:#00875a}/var/lib/jenkins/ParsingRuleFiles/Generic_Verify {color}}}than to fail a build , it should be something like : {quote}{{ finally {}}{{ node('__') {}}{{ try {}}{{ step([$class: '{color:#00875a}LogParserPublisher{color}', parsingRulesPath: '{color:#00875a}/var/lib/jenkins/ParsingRuleFiles/Generic_Verify{color}', useProjectRule: false, *{color:#403294}failBuildOnError{color}: {color:#de350b}true{color}, {color:#403294}unstableOnWarning{color}: {color:#de350b}true{color}*])}}{{ } catch(all) {}}{{ print "-E- LogParserPublisher failed: \n" +all }}{{ }}}{{ }//node}}{{}//finally}} {quote}{quote}{{tested - and working , me very happy :)}} {quote}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title
danniel hughes commented on JENKINS-32866
Re: Log Parser Plugin does not parse Pipeline console outputs
so, assuming the file of rules is {{/var/lib/jenkins/ParsingRuleFiles/Generic_Verify }}than fail a build it should be something like :
finally { node('') { try { step([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/ParsingRuleFiles/Generic_Verify', useProjectRule: false, *failBuildOnError: true, unstableOnWarning: true*]) } catch(all) { {{ print "E LogParserPublisher failed: \n" +all }} } }//node }//finally
tested - and working , me very happy
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Prince Raj Kumar updated an issue Jenkins / JENKINS-32866 Log Parser Plugin does not parse Pipeline console outputs Change By: Prince Raj Kumar Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
