[JIRA] (JENKINS-53755) Detect and publish Jacoco reports
Title: Message Title Tobias Schoeneberg edited a comment on JENKINS-53755 Re: Detect and publish Jacoco reports Hi, just as a quick feedback:we build a quick multi-module projects with each module creating its own jacoco report.We further use the [jacoco-plugin|https://plugins.jenkins.io/jacoco] to aggregate them into one report and show them on the respective build job's page.Now with this new feature (unless disabled, i hope) we get 85 the "Coverage report" and "Jacoco - Overall Coverage Summary" 85 times (all showing the same thing, btw), which pretty much kills the page.We had a similar problem before, when the plugin's auto-archiving (unless disabled) blew up our disk.Don't get me wrong, I appreciate your work and don't want to make reproaches. To make users like me *even happier* ;-), maybe you can also test the plugin with bigger code bases?I guess we have a relatively big one, which is also [open source and hosted on github|https://github.com/metasfresh/metasfresh]. If you want to use it for build-testing, I might be able to help you setting it up. 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-53755) Detect and publish Jacoco reports
Title: Message Title Tobias Schoeneberg edited a comment on JENKINS-53755 Re: Detect and publish Jacoco reports Hi, just as a quick feedback:we build a multi-module projects with each module creating its own jacoco report.We further use the [jacoco-plugin|https://plugins.jenkins.io/jacoco] to aggregate them into one report and show them on the respective build job's page.Now with this new feature (unless disabled , i hope ) we get 85 times the "Coverage report" and "Jacoco - Overall Coverage Summary" 85 times (all showing the same thing, btw), which pretty much kills the page.We had a similar problem before, when the plugin's auto-archiving (unless disabled) blew up our disk.Don't get me wrong, I appreciate your work and don't want to make reproaches. To make users like me *even happier* ;-), maybe you can also test the plugin with bigger code bases?I guess we have a relatively big one, which is also [open source and hosted on github|https://github.com/metasfresh/metasfresh]. If you want to use it for build-testing, I might be able to help you setting it up. 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-53755) Detect and publish Jacoco reports
Title: Message Title Tobias Schoeneberg commented on JENKINS-53755 Re: Detect and publish Jacoco reports Hi, just as a quick feedback: we build a quick multi-module projects with each module creating its own jacoco report. We further use the jacoco-plugin to aggregate them into one report and show them on the respective build job's page. Now with this new feature (unless disabled, i hope) we get 85 the "Coverage report" and "Jacoco - Overall Coverage Summary" 85 times (all showing the same thing, btw), which pretty much kills the page. We had a similar problem before, when the plugin's auto-archiving (unless disabled) blew up our disk. Don't get me wrong, I appreciate your work and don't want to make reproaches. To make users like me even happier , maybe you can also test the plugin with bigger code bases? I guess we have a relatively big one, which is also open source and hosted on github. If you want to use it for build-testing, I might be able to help you setting it up. 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-46809) Allow sequential stages inside parallel in Declarative syntax
Title: Message Title Hokwang Lee commented on JENKINS-46809 Re: Allow sequential stages inside parallel in Declarative syntax Please be interested in this JENKINS-53127 related issue. 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-53842) Upgrade Maven version used for Blue Ocean CI
Title: Message Title Olivier Lamy commented on JENKINS-53842 Re: Upgrade Maven version used for Blue Ocean CI pr https://github.com/jenkinsci/blueocean-plugin/pull/1819 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-53842) Upgrade Maven version used for Blue Ocean CI
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-53842 Upgrade Maven version used for Blue Ocean CI Change By: Olivier Lamy Assignee: Olivier Lamy 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-51716) Blueocean stuck in loading
Title: Message Title
Ken Morse commented on JENKINS-51716
Re: Blueocean stuck in loading
Am still stuck in loading as well, now using Jenkins 2.138.1 (LTS) and Blue Ocean 1.8.3. There is still a _javascript_ error which may be contributing to the problem: VM1191 blueocean-core-js.js:57938 Error fetching page TypeError: Cannot read property 'self' of undefined {{ at ActivityService.bunkerKey (VM1191 blueocean-core-js.js:57260)}} {{ at ActivityService.setItem (VM1191 blueocean-core-js.js:57303)}} {{ at executeAction (VM1191 blueocean-core-js.js:40729)}} {{ at ActivityService.res (VM1191 blueocean-core-js.js:40701)}} {{ at PipelineService._this.bunkerMapper (VM1191 blueocean-core-js.js:58269)}} {{ at PipelineService.setItem (VM1191 blueocean-core-js.js:57302)}} {{ at executeAction (VM1191 blueocean-core-js.js:40729)}} {{ at PipelineService.res (VM1191 blueocean-core-js.js:40701)}} {{ at VM1191 blueocean-core-js.js:57321}} {{ at Array.map ()}} {{ at PipelineService.setItems (VM1191 blueocean-core-js.js:57320)}} {{ at VM1191 blueocean-core-js.js:57922}} {{ at executeAction (VM1191 blueocean-core-js.js:40729)}} {{ at res (VM1191 blueocean-core-js.js:40701)}}
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-53831) Stop displaying warnings when using withMaven in a Kubernetes agent
Title: Message Title Cyrille Le Clerc updated JENKINS-53831 Jenkins / JENKINS-53831 Stop displaying warnings when using withMaven in a Kubernetes agent Change By: Cyrille Le Clerc Status: Fixed but Unreleased Closed 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-53831) Stop displaying warnings when using withMaven in a Kubernetes agent
Title: Message Title Cyrille Le Clerc updated JENKINS-53831 Fixed in 3.5.14 Jenkins / JENKINS-53831 Stop displaying warnings when using withMaven in a Kubernetes agent Change By: Cyrille Le Clerc Status: Open Fixed but Unreleased Resolution: Fixed 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-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title
Cyrille Le Clerc commented on JENKINS-53812
Re: jenkins pipeline maven build error when workspace contain Chinese characters
This sounds like a Maven exception more than a withMaven(){} exception. Can you introduce in your pipeline "ls -al" before invoking your Maven command?
...
withMaven() {
sh """
ls -al
mvn clean deploy
"""
}
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-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title
Cyrille Le Clerc commented on JENKINS-53812
Re: jenkins pipeline maven build error when workspace contain Chinese characters
This sounds like a Maven exception more than a withMaven(){} exception. Can you introduce in your pipeline "ls -al" before invoking your Maven command?
...
withMaven() {
sh """
ls -al
mvn clean deploy
"""
}
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-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-53812
Re: jenkins pipeline maven build error when workspace contain Chinese characters
This sounds like a Maven exception more than a withMaven(){} exception.Can you introduce in your pipeline "ls -al" before invoking your Maven command?{code:groovy}...withMaven() { sh """ls -almvn clean deploy"""}{code}
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-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-53812
Re: jenkins pipeline maven build error when workspace contain Chinese characters
This sounds like a Maven exception more than a withMaven(){} exception.Can you introduce in your pipeline "ls -al" before invoking your Maven command?{code :groovy } ...withMaven() { sh """ls -almvn clean deploy"""}{code}
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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Andrew a commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Devin Nusbaum, an update. It looks like I've got the hit the first try and now see a handful of [rumboot-default-rumboot-basis-Debug-basis-stress-test-uart-eth-dma] Cannot contact oribi: java.lang.InterruptedException [rumboot-default-rumboot-basis-Debug-simple-iram-mirror-hello-arinc_1] Cannot contact bison: java.lang.InterruptedException [rumboot-default-rumboot-basis-Debug-simple-iram-mirror-hello-arinc_6] Cannot contact oribi: java.lang.InterruptedException in the log. I now have the build in the stuck state and can provide the data. Can you tell a bit more detail of where to find the relevant XML files? A quick grep on the slaves didn't reveal any workflow directories. Where should I look for them? 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Andrew a updated an issue Jenkins / JENKINS-46507 Parallel Pipeline random java.lang.InterruptedException Change By: Andrew a Attachment: hs_err_pid239040.log 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-51948) ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent
Title: Message Title Joerg Schwaerzler commented on JENKINS-51948 Re: ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent Thanks for the fast reply. In that case I'll see whether the fix I need will possibly fix this one as well and document the PR accordingly. 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-39665) Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin
Title: Message Title Lubomir Stanko commented on JENKINS-39665 Re: Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin Bruno P. Kinoshita I've found some time to check and test it and I've created a pull request. Please check https://github.com/jenkinsci/active-choices-plugin/pull/21 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-51948) ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent
Title: Message Title Josh Soref commented on JENKINS-51948 Re: ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent I gave up trying to figure out how to fix this. When I work on things, I tend to post PR requests fairly quickly... Otherwise, I file bugs and hope someone else will fix... 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-51948) ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent
Title: Message Title Joerg Schwaerzler commented on JENKINS-51948 Re: ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent While working on JENKINS-36547 I came accross this issue. At least when running my unit tests it looks like computeEnclosingLabel() is not able to find the label for the parallel branches created in my test code. Is there someone already working on a fix? I'd like to avoid duplicate work here... 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-53827) on fedora 27 build. Jenkins will deliver blank content when started up.
Title: Message Title Oleg Nenashev commented on JENKINS-53827 Re: on fedora 27 build. Jenkins will deliver blank content when started up. It looks like a binary conflict with something: "java.lang.NoSuchMethodError: org.dom4j.io.HTMLWriter.setEnabled(Z)V". Most likely you tried to install a plugin requiring newer version of Jenkins. Whatever is the root cause, the most likely solution is to upgrade your instance. You use 1.651.3 which is more than 2 years old. 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-53827) on fedora 27 build. Jenkins will deliver blank content when started up.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53827 on fedora 27 build. Jenkins will deliver blank content when started up. Change By: Oleg Nenashev Component/s: core Component/s: jenkins-test-harness 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-53844) Each new HTTP query starts an infinite loop, burning CPU
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53844 Each new HTTP query starts an infinite loop, burning CPU Change By: Oleg Nenashev Component/s: next-executions-plugin Component/s: core 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-53844) Each new HTTP query starts an infinite loop, burning CPU
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53844 Each new HTTP query starts an infinite loop, burning CPU Change By: Oleg Nenashev Labels: performance 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-53844) Each new HTTP query starts an infinite loop, burning CPU
Title: Message Title Oleg Nenashev commented on JENKINS-53844 Re: Each new HTTP query starts an infinite loop, burning CPU at hudson.plugins.nextexecutions.utils.NextExecutionsUtils.getNextBuild(NextExecutionsUtils.java:56) at hudson.plugins.nextexecutions.NextExecutionsWidget.getBuilds(NextExecutionsWidget.java:80) Whatever is happening there, it's caused by the Next Executions plugin. It tries to process all items in the view without any caching: https://github.com/jenkinsci/next-executions-plugin/blob/master/src/main/java/hudson/plugins/nextexecutions/NextExecutionsWidget.java#L54-L109 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-53847) Improve JavaDoc for Util.fixNull
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53847 Improve JavaDoc for Util.fixNull Change By: Oleg Nenashev Issue Type: Task Improvement 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-53847) Improve JavaDoc for Util.fixNull
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-53847 Improve JavaDoc for Util.fixNull Issue Type: Task Assignee: Unassigned Components: core Created: 2018-09-30 11:39 Labels: newbie-friendly Priority: Trivial Reporter: Wadeck Follonier During #3656 we discover that the return value of Util.fixNull for collection (Iterable, List, Set and Collection) returns unmodifiable collections and that is not written in the JavaDoc. Objective: improve the JavaDoc of four methods (overload of fixNull) related in hudson.Util. Add Comment
[JIRA] (JENKINS-53846) scm sync configuration plugin
Title: Message Title gopi ksng created an issue Jenkins / JENKINS-53846 scm sync configuration plugin Issue Type: Bug Assignee: Craig Rodrigues Components: scm-sync-configuration-plugin Created: 2018-09-30 11:27 Environment: while configuring the plugin if scm sync configuration with Jenkins i am facing error Priority: Critical Reporter: gopi ksng 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
[JIRA] (JENKINS-53845) Refactor CLI Return code to avoid magical numbers everywhere
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-53845 Refactor CLI Return code to avoid magical numbers everywhere Issue Type: Improvement Assignee: Wadeck Follonier Components: cli Created: 2018-09-30 09:13 Priority: Minor Reporter: Wadeck Follonier Context: JENKINS-32273 introduces better readability of the different error scenario in CLI by catching lots of exceptions. Now the problem is that the different catch are returning error code that are pure integer. It's especially hard to understand / follow / find the meaning of all those values if we are not aware they are listed somewhere. Proposed solution: Using an interface as the return type (and keeping the existing method for binary compability) with a standard return code enum implementing the interface for the core and the possibility for plugins to implement their own enum for the custom codes. That will allow the future developers to have "easy link" to the description of the code or even directly the meaning by reading the name of the enum that is used. Add Comment
[JIRA] (JENKINS-52685) Publish over SSH cannot add server
Title: Message Title aihua w commented on JENKINS-52685 Re: Publish over SSH cannot add server Alex Earl Yes, it is the whole Configure System screen, and nothing below. 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.
