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

Polling no longer triggering builds after Jenkins upgrade to 1.651.2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
    • Environment:
      Linux localhost.privatedomain x86_64 GNU/Linux, Jenkins 1.651.2, Debian Jessie, Java 8
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            kurt Kurt Nuke added a comment -

            Worked around this issue with a HTTP Request Post Receive hook from Stash to Jenkins.

            Show
            kurt Kurt Nuke added a comment - Worked around this issue with a HTTP Request Post Receive hook from Stash to Jenkins.
            Hide
            panajev Goffredo Marocchi added a comment -

            Both post receive hooks from GitHub Enterprise and SCM polls fail, on all the jobs I have configured, so I cannot use your workaround. This did not happen with the upgrade mentioned in the title, but well after Jenkins 2.x released (it was working with Jenkins 2.0 by the way).

            What logs could I collect to help out with this issue?

            Show
            panajev Goffredo Marocchi added a comment - Both post receive hooks from GitHub Enterprise and SCM polls fail, on all the jobs I have configured, so I cannot use your workaround. This did not happen with the upgrade mentioned in the title, but well after Jenkins 2.x released (it was working with Jenkins 2.0 by the way). What logs could I collect to help out with this issue?
            Hide
            evilrix Ricky Cormier added a comment -

            Is there any update on this issue? We are also having a similar issue. We have a master node running on Linux (AWS), which we use to start up Windows nodes (also AWS). We use the Slave Setup Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Slave+Setup+Plugin) to start nodes on demand; however, jobs are not being scheduled because Jenkins sees all nodes offline. As I understand it, this plugin only starts nodes if there are jobs scheduled. Clearly, there is an inconsistency between Jenkins and this plugin.

            Show
            evilrix Ricky Cormier added a comment - Is there any update on this issue? We are also having a similar issue. We have a master node running on Linux (AWS), which we use to start up Windows nodes (also AWS). We use the Slave Setup Plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Slave+Setup+Plugin ) to start nodes on demand; however, jobs are not being scheduled because Jenkins sees all nodes offline. As I understand it, this plugin only starts nodes if there are jobs scheduled. Clearly, there is an inconsistency between Jenkins and this plugin.
            Hide
            vighnesh_p Vighnesh Pai added a comment -

            Ricky Cormier, I'm also facing the same issue. Did you ever get to resolve this? If so, please let me know. I'm using Jenkins 2.138.1 LTS version. and my configs are almost the same as yours.

             

            Show
            vighnesh_p Vighnesh Pai added a comment - Ricky Cormier , I'm also facing the same issue. Did you ever get to resolve this? If so, please let me know. I'm using Jenkins 2.138.1 LTS version. and my configs are almost the same as yours.  
            Hide
            northgorky Steve Davidson added a comment -

            Seen in Jenkins 2.249.1

            Show
            northgorky Steve Davidson added a comment - Seen in Jenkins 2.249.1

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              kurt Kurt Nuke
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated: