Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-54854

Warning when trigger spent to much time in a cron execution

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 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.

          [JENKINS-54854] Warning when trigger spent to much time in a cron execution

          Pavel Janoušek created issue -
          Pavel Janoušek made changes -
          Summary Original: Warning when trigger spent to much time in cron execution New: Warning when trigger spent to much time in a cron execution
          Pavel Janoušek made changes -
          Description Original: 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).
          New: 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 Original: Open [ 1 ] New: In Progress [ 3 ]
          Pavel Janoušek made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Pavel Janoušek made changes -
          Remote Link New: This issue links to "PR (Web Link)" [ 22097 ]
          Oliver Gondža made changes -
          Description Original: 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).
          New: 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.
          Oliver Gondža made changes -
          Link New: This issue relates to JENKINS-19123 [ JENKINS-19123 ]
          Oleg Nenashev made changes -
          Released As New: Jenkins 2.189
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]
          Oleg Nenashev made changes -
          Status Original: Resolved [ 5 ] New: Fixed but Unreleased [ 10203 ]
          Oleg Nenashev made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]

            pajasoft Pavel Janoušek
            pajasoft Pavel Janoušek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: