Polling no longer triggering builds after Jenkins upgrade to 1.651.2

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Critical
    • Component/s: core
    • Environment:
      Linux localhost.privatedomain x86_64 GNU/Linux, Jenkins 1.651.2, Debian Jessie, Java 8

      As of this upgrade Polling on random repos hosted on our Bitbucket Server has stopped working. At the same time of this occurrence one of our build nodes went offline due to a hardware issue, though all builds have been migrated to new nodes.

      SCM polling set to H**** (every hour)

      The polling log states:

      Started on May 19, 2016 1:34:00 PM
      We need to schedule a new build to get a workspace, but deferring 86,256ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
      Done. Took 24 ms
      No changes
      

      The build does have a workspace, though – me and our system administration team are stumped.

      The node that it is selected to build on is online and other builds are triggering and building there just fine and creating Workspaces without issue.

      Copying the Job leads to the same result after the first change noticed by the SCM polling.

            Assignee:
            Unassigned
            Reporter:
            Kurt Nuke
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: