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

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

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins 1.448 RC
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Show
            abayer Andrew Bayer added a comment - Looks to be related to/caused by https://github.com/jenkinsci/jenkins/commit/b1bb3f66676b550971db08725d5c3cef5b42191b
            Hide
            ohtake_tomohiro OHTAKE Tomohiro added a comment -

            As Sogabe has resolved JENKINS-12356, JENKINS-12388 has been resolved too.
            Pull-344 has some test code
            which checks if crontab will be eventually triggered or not.
            Though the issue has been resolved, the test would be useful.

            Show
            ohtake_tomohiro OHTAKE Tomohiro added a comment - As Sogabe has resolved JENKINS-12356 , JENKINS-12388 has been resolved too. Pull-344 has some test code which checks if crontab will be eventually triggered or not. Though the issue has been resolved, the test would be useful.
            Hide
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #1512
            [FIXED JENKINS-12388] Add tests for JENKINS-12388 (Revision 240c381bb867873da8dc4984acc199b243aea48e)

            Result = SUCCESS
            ohtake.tomohiro : 240c381bb867873da8dc4984acc199b243aea48e
            Files :

            • core/src/test/java/hudson/scheduler/CronTabEventualityTest.java
            Show
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #1512 [FIXED JENKINS-12388] Add tests for JENKINS-12388 (Revision 240c381bb867873da8dc4984acc199b243aea48e) Result = SUCCESS ohtake.tomohiro : 240c381bb867873da8dc4984acc199b243aea48e Files : core/src/test/java/hudson/scheduler/CronTabEventualityTest.java
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: OHTAKE Tomohiro
            Path:
            core/src/test/java/hudson/scheduler/CronTabEventualityTest.java
            http://jenkins-ci.org/commit/jenkins/240c381bb867873da8dc4984acc199b243aea48e
            Log:
            [FIXED JENKINS-12388] Add tests for JENKINS-12388

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/test/java/hudson/scheduler/CronTabEventualityTest.java http://jenkins-ci.org/commit/jenkins/240c381bb867873da8dc4984acc199b243aea48e Log: [FIXED JENKINS-12388] Add tests for JENKINS-12388

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: