|
||||||||
|
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.
Did you even read my entire comment before commenting on it?
"I just implemented Oleg's suggested solution..."
And where in my comments do I mention anything about a disconnect? How are any further jobs supposed to be executed on an offline node? Coming in the next day with the remainder of my build jobs queued up due to falling below the disk space threshold is not desirable.
And another thing...I don't want emails every time the node goes offline because I've got something in my process that restarts the slave machine - by design. I just want an email when disk space falls below the threshold.
So obviously I tried the solution. I just assumed I must have misinterpreted the fairly ambiguous description for the solution to come with this much "baggage".