Closed timja closed 12 years ago
Looks to be related to/caused by https://github.com/jenkinsci/jenkins/commit/b1bb3f66676b550971db08725d5c3cef5b42191b
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.
Integrated in jenkins_main_trunk #1512
[FIXED JENKINS-12388] Add tests for JENKINS-12388 (Revision 240c381bb867873da8dc4984acc199b243aea48e)
Result = SUCCESS
ohtake.tomohiro : 240c381bb867873da8dc4984acc199b243aea48e
Files :
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
[Originally related to: JENKINS-12356]
Steps to reproduce:
@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-12356is fixed, this issue will be also fixed.Originally reported by ohtake_tomohiro, imported from: Crontab @yearly and @anually are never triggered in 1.448 RC