Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
-
Jenkins 2.189
Description
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.
Attachments
Issue Links
- relates to
-
JENKINS-19123 ghprb prevents Jenkins cron thread from running
-
- In Review
-
- links to
Activity
Pavel Janoušek
created issue -
Pavel Janoušek
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Warning when trigger spent to much time in cron execution | Warning when trigger spent to much time in a cron execution |
Pavel Janoušek
made changes -
| Description |
It would be nice to 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). |
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). |
Pavel Janoušek
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Pavel Janoušek
made changes -
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
Pavel Janoušek
made changes -
| Remote Link | This issue links to "PR (Web Link)" [ 22097 ] |
| Description |
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). |
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. |
| Link | This issue relates to JENKINS-19123 [ JENKINS-19123 ] |
| Released As | Jenkins 2.189 | |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10005 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Fixed but Unreleased [ 10203 ] |
| Status | Fixed but Unreleased [ 10203 ] | Resolved [ 5 ] |