When a maintenance window is started by Agent Maintenance plugin, Jenkins considers this as SCM change

XMLWordPrintable

    • Type: Bug
    • Resolution: Not A Defect
    • Priority: Minor
    • Component/s: agent-maintenance-plugin
    • None
    • Environment:
      Windows Server installation of Jenkins LTS 2.426.3.
      Agent Maintenance plugin version 2.163.v08874cd79262

      When a maintenance window is started, Jenkins considers this as SCM change and all builds needlessly start and fill the build queue. After the maintenance window is over, all the build agents get busy performing builds, potentially causing builds triggered by real SCM changes to wait for several hours due to the queue.

      Example:

      Console Output

       
      09:19:00 Started by an SCM change
       

            Assignee:
            Markus Winter
            Reporter:
            Peter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: