|
||||||||||||||
|
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.
Not a Jenkins bug, but a bug in the build script or the tools being called that should be able to determine that they're not writing their output to an interactive shell. From Jenkins, what happens should be indistinguishable from a well-behaving build.
Aborting running builds before space runs out seems pointless, because on a Jenkins server, builds getting aborting because space has run out appears to be the most severe result.
Plugins like Logfilesizechecker and build-timeout plugin do the job wrt automatically determinable misbehaving builds.