[JIRA] (JENKINS-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner updated JENKINS-55357 Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner updated JENKINS-55357 Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Assignee: Ulli Hafner 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Component/s: warnings-ng-plugin Component/s: javadoc-plugin 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner commented on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log You can provide a custom name as well. Changing the URLs in general is somewhat dangerous since the 1.0 release is out now. And I think there are no other tools that actually have a URL. So I think the best is to add a suffix as soon as someone encounters a problem. 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson commented on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log That seems to work barring a UI discrepancy. Javadoc warnings shows up as a generic "Static Analysis" entry but the URLs are functional. I used javadoc-warn just for the test and the arrows show the result. Given the number of formats the new plugin supports maybe it would help to prefix them all with warn to avoid collisions? For example: server/job/Customer/96/warncheckstyle /warnjavadoc /warneclipse 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson updated an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Michael Thompson Attachment: 2019-01-03_12-18-37.png 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner edited a comment on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log Ah, yes of course. The javadoc archiver is using the same URL. Can you assign a custom id for the java doc part parser and retry? I think I need to change the default ID to something different, may be java-doc? Or do you have a better idea for a name? 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner commented on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log Ah, yes of course. The javadoc archiver is using the same URL. Can you assign a custom id for the java doc part and retry? I think I need to change the default ID to something different, may be java-doc? Or do you have a better idea for a name? 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson updated an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Michael Thompson Attachment: 2019-01-02_15-29-54.png 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson commented on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log I'll attach a photo. It happens when I click on the links in the side bar, main section or the info icon. They lead to URLs of the form: http://server:8081/job/CUSTOMER_Market/159/javadoc/info or http://server:8081/job/CUSTOMER_Market/159/javadoc/ The root of the project actual Javadoc link works. Could the "Publish Javadoc" post build action be colliding with the warnings plugin? http://server:8081/job/CUSTOMER_Market/javadoc 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner assigned an issue to Unassigned The stack trace is from the JavaDoc plugin and not from the warnings plugin. Which link did you click? Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Component/s: javadoc-plugin Component/s: warnings-ng-plugin Assignee: Ulli Hafner 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson created an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Issue Type: Bug Assignee: Ulli Hafner Attachments: trace.txt Components: warnings-ng-plugin Created: 2018-12-28 21:25 Environment: OS: Win 2008 Server R2 64bit Java: Oracle 1.8.0_171-b11 Jenkins: 2.150.1 warnings 5.0.0 warnings-ng 1.0.0 Priority: Minor Reporter: Michael Thompson After upgrading activated the new warnings plugin. It appears to parse the console log. Clicking on the link afterward in the project screen throws an error. [JavaDoc] Sleeping for 5 seconds due to JENKINS-32191... [JavaDoc] Parsing console log (workspace: 'C:\PCI_Dev\source\pcisvn\CUSTOMER\CUSTOMER_Market\Code\CUSTOMER_Market') [JavaDoc] Post processing issues on 'Master' with encoding 'windows-1252' [JavaDoc] Resolving absolute file names for all issues [JavaDoc] -> 0 resolved, 0 unresolved, 31 already resolved [JavaDoc] Copying affected files to Jenkins' build folder C:\Program Files (x86)\Jenkins\jobs\CUSTOMER_Market\builds\84 [JavaDoc] -> 31 copied, 0 not in workspace, 0 not-found, 0 with I/O error [JavaDoc] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files) [JavaDoc] -> resolved module names for 65 issues [JavaDoc] Resolving package names (or namespaces) by parsing the affected files [JavaDoc] -> resolved package names of 32 affected files [JavaDoc] No filter has been set, publishing all 65 issues [JavaDoc] Creating fingerprints for all affected code blocks to track issues over different builds
