|
||||||||||||||
|
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.
Correction: in the US, ⅓ of jobs would experience only the skipped run in the spring; another ⅓ would experience only the doubled run in the fall (for jobs for which H(0-2) resolves to 1). So only compressing the macro all the way to H 0 * * * would work in the US, and this might result in unacceptably high server load at night. Furthermore, variant policies in other countries (such as in Europe) might require different changes.
It seems that the only safe course of action for a Jenkins administrator is to set the server to use UTC. Ideally any times displayed by the system would still use the timezone requested by the browser, but the REST API and crontab form input would use UTC.