|
||||||||||||||
|
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.
I don't like the fix, personally. And I also don't think it satisfied the original request which allows no room for an offline node. I just implemented Oleg's suggested solution, but my complaint with it is that it takes the node (master or slave) offline in order to achieve the desired notification. That means I could very well have a build in progress when free disk space falls below the setting, and then the node will be taken offline. That's not at all what I want! I want to be proactive, and set a threshold that lets me know I'm running a bit low on disk space so that I can address it BEFORE it impacts a single build. Node monitoring and notification based on online/offline status certainly does not meet that need. At that point it's still too late. Whether I run out of disk space or the node goes offline, the result is the same - I've just failed a build.
Please feel free to correct me if I misinterpreted the resolution, as it seemed a bit open to interpretation.