-
Bug
-
Resolution: Fixed
-
Major
It would be nice if the cron expression took an optional timezone, this way I could schedule jobs in New York or the UK relative to them, rather than converting to central time. Also, since UK and the US observe daylight saving at different times, I have to adjust jobs an hour until both have converged
- links to
Thanks. This works for the scheduling, but if you kick off a shell script that uses the date command, it still assumes the host/slaves timezone and returns the wrong value. You can set an export variable before launching the script: export TZ=/usr/share/zoneinfo/Europe/London which will do the right thing, but now has to be managed in multiple places. Perhaps adding a dropdown with zones to the config that you can select makes more sense. Then the cron trigger and shell build task can interrogate and do the right thing if set.