|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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.
We no longer reproduce this as we worked around it by redirecting the output somewhere. It is far less likely we will see it as we've internalised this as a standard thing - we only allow small bits of glue code output to the main log, and archive the redirected output.
Where there are non-concurrent jobs, this also means it can be observed in the workspace.
Where we allow concurrent jobs and slave node labels, we have placed apache servers pointing at the workspace directories so we can easily view the in progress logs, and write the link to them out in the main console log when it starts up.