Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22106

@midnight is vulnerable to DST witching hours

    XMLWordPrintable

Details

    Description

      For servers using local time in regions with daylight saving time, twice a year there are "witching hours" for cron-like scheduling: a task scheduled for between 2:00 (AM, inclusive) and 3:00 (exclusive) will skip a day in the spring, and run twice on a single day in the fall. Unfortunately the @midnight macro in Jenkins is defined as H H(0-2) * * *, which for ⅓ of jobs will trigger the DST problem.

      Perhaps it should be redefined as H H(0-1) * * * to avoid this? During upgrade this would cause a one-time occasion when some jobs run 23 hours after the last run, which is not great but probably not a big deal. And it compresses the "midnight" range unnecessarily for servers using (say) UTC.

      Attachments

        Issue Links

          Activity

            jglick Jesse Glick created issue -
            jglick Jesse Glick made changes -
            Field Original Value New Value
            Resolution Won't Fix [ 2 ]
            Status Open [ 1 ] Resolved [ 5 ]
            mwebber Matthew Webber made changes -
            Labels cron GMT UTC cron
            mwebber Matthew Webber made changes -
            Link This issue is related to JENKINS-19977 [ JENKINS-19977 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 154185 ] JNJira + In-Review [ 194817 ]

            People

              Unassigned Unassigned
              jglick Jesse Glick
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: