[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Stefan Thurnherr commented on JENKINS-58977 Re: publishIssues() should use default ID instead of ID of first scan tool in list Ulli Hafner Works like a charm - thanks Ulli! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.201326.1566161283000.10951.1571515140311%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Stefan Thurnherr closed an issue as Fixed Jenkins / JENKINS-58977 publishIssues() should use default ID instead of ID of first scan tool in list Change By: Stefan Thurnherr Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.201326.1566161283000.10954.1571515140363%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Ulli Hafner updated JENKINS-58977 Jenkins / JENKINS-58977 publishIssues() should use default ID instead of ID of first scan tool in list Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: 6.0.0 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.201326.1566161283000.6158.1567551960834%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Ulli Hafner updated JENKINS-58977 Jenkins / JENKINS-58977 publishIssues() should use default ID instead of ID of first scan tool in list Change By: Ulli Hafner Status: In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201326.1566161283000.5373.1566210240260%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Ulli Hafner started work on JENKINS-58977 Change By: Ulli Hafner Status: Open In Progress 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.201326.1566161283000.4593.1566164040398%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-58977 publishIssues() should use default ID instead of ID of first scan tool in list Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/179 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.201326.1566161283000.4587.1566163920177%40Atlassian.JIRA.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title
Stefan Thurnherr updated an issue
Jenkins / JENKINS-58977
publishIssues() should use default ID instead of ID of first scan tool in list
Change By:
Stefan Thurnherr
When using several {{scanForIssues()}} steps and a single {{publishIssues()}} step at the end, the default id used for {{publishIssues()}} should be 'analysis', not taken from the first tool in the scanned tools list.Here is a simple example:{noformat}def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml')def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')def taskScannerIssues = scanForIssuestool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**')def javaIssues = scanForIssues tool: java()def mavenConsoleIssues = scanForIssues tool: mavenConsole()publishIssues name: 'Static Analysis',issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues]{noformat}In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for {{publishIssues()}} step.*Expected behaviour* would be that the default ID is 'analysis' when using {{publishIssues()}} without specifying a custom ID. (follow-up from [gitter discussion 2019-08-18|https://gitter.im/jenkinsci/warnings-plugin?at=5d59b9ffbfd2887f53146b16])
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title Stefan Thurnherr created an issue Jenkins / JENKINS-58977 publishIssues() should use default ID instead of ID of first scan tool in list Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-08-18 20:48 Environment: Jenkins 2.189 warnings-ng 5.3.0 Priority: Minor Reporter: Stefan Thurnherr When using several scanForIssues() steps and a single publishIssues() step at the end, the default id used for publishIssues() should be 'analysis', not taken from the first tool in the scanned tools list. Here is a simple example: def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml') def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml') def taskScannerIssues = scanForIssues tool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**') def javaIssues = scanForIssues tool: java() def mavenConsoleIssues = scanForIssues tool: mavenConsole() publishIssues name: 'Static Analysis', issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues] In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for publishIssues() step. *Expected behaviour * would be that the default ID is 'analysis' when using publishIssues() without specifying a custom ID.
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title
Stefan Thurnherr updated an issue
Jenkins / JENKINS-58977
publishIssues() should use default ID instead of ID of first scan tool in list
Change By:
Stefan Thurnherr
When using several {{ scanForIssues() }} steps and a single {{ publishIssues() }} step at the end, the default id used for {{ publishIssues() }} should be 'analysis', not taken from the first tool in the scanned tools list.Here is a simple example:{noformat}def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml')def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')def taskScannerIssues = scanForIssuestool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**')def javaIssues = scanForIssues tool: java()def mavenConsoleIssues = scanForIssues tool: mavenConsole()publishIssues name: 'Static Analysis',issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues]{noformat}In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for {{publishIssues()}} step.*Expected behaviour* would be that the default ID is 'analysis' when using {{publishIssues()}} without specifying a custom ID.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-58977) publishIssues() should use default ID instead of ID of first scan tool in list
Title: Message Title
Stefan Thurnherr updated an issue
Jenkins / JENKINS-58977
publishIssues() should use default ID instead of ID of first scan tool in list
Change By:
Stefan Thurnherr
When using several scanForIssues() steps and a single publishIssues() step at the end, the default id used for publishIssues() should be 'analysis', not taken from the first tool in the scanned tools list.Here is a simple example:{noformat}def pmdIssues = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml')def cpdIssues = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')def taskScannerIssues = scanForIssuestool: taskScanner(normalTags: 'TODO,FIXME', excludePattern: '*/target/**')def javaIssues = scanForIssues tool: java()def mavenConsoleIssues = scanForIssues tool: mavenConsole()publishIssues name: 'Static Analysis',issues: [pmdIssues, cpdIssues, taskScannerIssues, javaIssues, mavenConsoleIssues]{noformat}In the current version of warnings-ng plugin, the build will use 'pmd' as ID for links and controlling the icon when not specifying a custom ID for {{publishIssues()}} step.*Expected behaviour * would be that the default ID is 'analysis' when using {{publishIssues()}} without specifying a custom ID.
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
