The discussion of the new sessionTimeout parameter has piqued my interest.
One of my biggest problems in managing our Jenkins server is finding a time when I can restart it. We have many long running (>8 hr) test jobs that I hate to cancel because of the time investment already committed. We have made efforts to split the long jobs into sub jobs, but even 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.) Will a large value for the new -sessionTimeout parameter allow jobs on slaves to reconnect to a Jenkins server after the server is restarted? Richard -- 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.
