mwebber commented on New Feature JENKINS-13140

I ended up changing my slaves to "take this slave on-line when in demand and off-line when idle", and as suggested set

in demand delay = 0
idle delay = 1000000

That does not actually fix the problem, but it's good enough for me:

  • When Jenkins (re)starts, the slave process does not.
  • At the time a slave is required by a job, the slave process is started.
  • If I disconnect a slave, it stays disconnected until a job requires it, at which point it is restarted. At least it stays disconnected until required, rather than being reconnected almost immediately.


I did not try the keep-slave-disconnected-plugin (thanks for contributing though). To my mind this is solving the problem in the wrong place - the muddle and poor handling needs to be fixed in core, rather than overridden.

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.

Reply via email to