|
||||||||
|
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/groups/opt_out.
mwebber: Instead of only disconnecting, configure the slave to also have an in demand connection delay of 1000000. Works like a charm.
It'd be better if slave processes weren't started while they're marked offline, then you could just configure all your slaves with in demand delay 0/idle delay 1000000 and have effectively regular 'always on' slaves that don't automatically reconnect. Maybe this can be improved in core.
Since the user reporting this issue originally mentioned that the goal was accomplished through "mark offline", it'd help if anyone interested in this could provide a use case. Starting new builds can be prevented after all.