Daniel Beck commented on Improvement JENKINS-2107

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. Effectively that is a failed build.

You wrote:

… have a build in progress when free disk space falls below the setting, and then the node will be taken offline. … I want to be proactive, … BEFORE it impacts a single build.

A build that is already in progress is never impacted by marking a node offline. Hence my interpretation that you thought node monitors disconnected nodes. Re-reading that, I probably misunderstood that last part to mean the build in progress, rather than any build.


So there should probably be two thresholds for every node monitor: One soft (admin monitor preferably, i.e. a warning on the /manage page), one hard (marking the node offline).

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.

Reply via email to