[JIRA] (JENKINS-54759) Groovy Parsers

[nolang...@gmail.com (JIRA)]

Title: Message Title

Norbert Lange created an issue   Jenkins / JENKINS-54759 Groovy Parsers Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-11-21 17:35 Environment: Jenkins ver. 2.138.3 (Docker Hub) Wanings NG 1.0.0-beta5 Priority: Minor Reporter: Norbert Lange The configuration and functionality is currently lacking 1) The help text under the Static Analysis Tool configuration (Freestyle job), should add that the own configured Parser can be found if "Groovy Parser" is selected   For each static analysis tool a dedicated parser will be used to read the report files. If your tool is not yet supported then you can create your own parser in the system configuration.   2) Groovy Parser cant scan console log output ?! Seems a bit weird to me that a single scanner has this limitation, is this getting fixed, or is there a recommendation to start writing logs to a file first? (As in best practices, generally for Jenkins or specific to this plugin). like using "2>&1 | tee some.log" on commands?   FATAL: Static analysis tool Groovy Parser cannot scan console log output, please define a file pattern     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.