Crontab @yearly and @anually are never triggered in 1.448 RC

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Steps to reproduce:

      1. Install Jenkins 1.448 RC
      2. Create a free-style job and set its "Build periodically" schedule to @yearly
      3. Stop Jenkins
      4. Adjuest server's time to 2012-12-31 23:55
      5. Start Jenkins
      6. Wait until 2013-01-01, but the job is not triggerd

      @yearly and @annually were interpreted to "0 0 1 1 *" by Jenkins 1.447.
      On the other hand they are interpreted to "H H H H *" by Jenkins 1.448 RC
      and "H" are hashed to "0 0 1 0 *".
      Since there is no chanse for month to be 0,
      @yearly and @annually are never triggered in 1.448 RC.

      Workaround:
      Instead of @yearly and @annually, use "0 0 1 1 *".

      If JENKINS-12356 is fixed, this issue will be also fixed.

            Assignee:
            OHTAKE Tomohiro
            Reporter:
            OHTAKE Tomohiro
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: