On 18.12.2013, at 19:11, Richard J Otter <r...@columbia.edu> wrote: > Will a large value for the new –sessionTimeout parameter allow jobs on slaves > to reconnect to a Jenkins server after the server is restarted?
It's just for HTTP sessions, not for slave connections. OTOH, it's enough to reload config from disk for most changes to job data and config files (which doesn't lose running builds) -- and if you restart to update plugins, continuing builds on slaves with mismatched code between master and slaves would likely be a bad idea. > the job queue is lost after a restart and we have to reschedule the sub jobs > (with the needed parameters that were lost with the queue.) The queue should survive a regular restart. It does on my Jenkins. See this feature mentioned e.g. here: http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/aborted-builds.html "If any jobs were waiting in the scheduler queue at the time of the crash, they will still be there after a restart." -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
