[JIRA] (JENKINS-54759) Groovy Parsers

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

Title: Message Title

Norbert Lange commented on JENKINS-54759   Re: Groovy Parsers Scanning of the console log is done on the master currently, all other files are scanned on the agent....Do you have a better idea? I would try to move all processing to the agent(s), its not obvious to me why this split exists (has to exist). Can’t you pipe your log output to a file on the agent? Yes I can, but not without issues. Some variants: not piping would be the most clear, and similar to the scripts you would run on a local build piping it just to a file will remove all visible status during execution naively splitting it (eg. | tee file.log) will mean the error state of the script doing the build will vanish. see here additionally storing and restoring the errors state of the script adds boilerplate code That's why I asked about a recommendation (a bug tracker is the wrong place, but you don't have a forum?) As for the split, keep the help-text issue here, and handle the rest in JENKINS-52237? 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.