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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Jenkins 1.448 RC

      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.

          [JENKINS-12388] Crontab @yearly and @anually are never triggered in 1.448 RC

          OHTAKE Tomohiro created issue -
          OHTAKE Tomohiro made changes -
          Link New: This issue is related to JENKINS-12356 [ JENKINS-12356 ]
          OHTAKE Tomohiro made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          OHTAKE Tomohiro made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          OHTAKE Tomohiro made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 142754 ] New: JNJira + In-Review [ 205601 ]

            ohtake_tomohiro OHTAKE Tomohiro
            ohtake_tomohiro OHTAKE Tomohiro
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: