As the originator of this thread, thanks for your responses. We're on Linux, so the Windows concerns thankfully don’t apply.
As stated, the usual way to handle this kind of thing is for the server to keep time in UTC, and the application converts to local time for display etc. purposes. The application, in this case, is Jenkins, and it doesn’t look like it really handles this properly - it does everything in local time, and gets confused with the summer time change. Generally, local time in the Jenkins interface is what _I_ want. When I write a job schedule, I want the times to be local -I think of a job as running at 10pm local time, and not the UTC equivalent. Other Jenkins installations may have different requirements as well, of course. Users and slaves can be in a different time zone to the master. -- 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/d/optout.
