-
Bug
-
Resolution: Fixed
-
Critical
-
None
We use the next expression to trigger job each Monday at 11:00
0 11 * * 1
We are facing with issue when Cron PeriodicWork start execution on the end of the minute.
Feb 08, 2024 10:59:59 AM FINE org.jenkinsci.plugins.parameterizedscheduler.Cron cron checking job1 Feb 08, 2024 10:59:59 AM FINE org.jenkinsci.plugins.parameterizedscheduler.Cron cron checking job2 Feb 08, 2024 11:00:00 AM FINE org.jenkinsci.plugins.parameterizedscheduler.Cron cron checking job3 Feb 08, 2024 11:00:00 AM FINE org.jenkinsci.plugins.parameterizedscheduler.Cron cron checking job4
As we can see, in this case some triggers are checked in scope of current minute (minute of starting periodic work), next part - in scope of future minute. Therefore it is possible that some 'boundary' trigger can be checked using current minute of the first time (10:59) and using future minute of the second time (11:01) and current minute of the second time (11:00) will be never used for checking our 'boundary' trigger