[ https://issues.jenkins-ci.org/browse/JENKINS-12388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
OHTAKE Tomohiro resolved JENKINS-12388. --------------------------------------- Resolution: Fixed > Crontab @yearly and @anually are never triggered in 1.448 RC > ------------------------------------------------------------ > > Key: JENKINS-12388 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12388 > Project: Jenkins > Issue Type: Bug > Components: core > Environment: Jenkins 1.448 RC > Reporter: OHTAKE Tomohiro > Assignee: OHTAKE Tomohiro > > Steps to reproduce: > # Install Jenkins 1.448 RC > # Create a free-style job and set its "Build periodically" schedule to @yearly > # Stop Jenkins > # Adjuest server's time to 2012-12-31 23:55 > # Start Jenkins > # 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira