-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
Jenkins 2.189
It would be nice make a warning to a log when Trigger spends too much time in Cron trigger.
It ssually means a malfunction or other issue in a plug-in and timers initiated by defined crontab(s) aren't working correctly (at least when expected). Given Jenkins cron task design, trigger taking more than 60 seconds to complete can prevent task scheduled for the next minute to run on time.
- relates to
-
JENKINS-19123 ghprb prevents Jenkins cron thread from running
- In Review
- links to