|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Regarding the "== Why someone would have 4MB of stderr output =="
Some of us use Jenkins for things like running Maven builds which have a goal of "integration-test". In other words, there is very little 'build' in the traditional sense, and in fact the 'build' itself may not even be unit tests associated with a build of a product-under-test, but an entirely separate test project being built that interacts with something completely external. This generates reams and reams of output from testNG tests, etc, and there might be a valid reason to use stderr in some of that output. Couple that with potentially thousands of tests... Just adding this commentary in case it helps people think of scenarios like this. We use it in this fashion nightly.