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

Polling no longer triggers builds (regression 1.560)

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Linux localhost.localdomain 2.6.32-431.1.2.el6.x86_64 #1 SMP Thu Dec 12 13:59:19 CST 2013 x86_64 x86_64 x86_64 GNU/Linux

      As of version 1.560, polling my private mercurial repository hosted by BitBucket no longer works. Before version 1.560 this worked as expected. Other than Jenkins itself, there were no other changes to the system. The poll configuration looks like:

      H/5 * * * *

      The "poll log" says the following:

      Started on Apr 24, 2014 8:08:05 AM
      We need to schedule a new build to get a workspace, but deferring 1,149ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
      Done. Took 1 ms
      No changes
      

      The build does have a valid workspace. Doing a manual build to "get a workspace" does work but does not resolve the polling issue.

      This is a single Jenkins instance without any slaves.

      I'd be happy to provide any other logs, information, or tests required to resolve this issue.

          [JENKINS-22750] Polling no longer triggers builds (regression 1.560)

          Jon Dufresne created issue -

          Jon Dufresne added a comment -

          Jon Dufresne added a comment - This discussion among users looks to be describing the same issue: http://jenkins-ci.361315.n4.nabble.com/No-new-jobs-are-created-after-upgrading-to-1-560-polling-plugin-reports-no-changes-when-there-are-td4699709.html
          Jon Dufresne made changes -
          Description Original: As of version 1.560, polling my private mercurial repository hosted by BitBucket no longer works. Before version 1.560 this worked as expected. Other than Jenkins itself, there were no other changes to the system. The poll configuration looks like:

          H/5 * * * *

          The "poll log" says the following:

          {{{
          Started on Apr 24, 2014 8:08:05 AM
          We need to schedule a new build to get a workspace, but deferring 1,149ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
          Done. Took 1 ms
          No changes
          }}}

          The build does have a valid workspace. Doing a manual build to "get a workspace" does work but does not resolve the polling issue.

          This is a single Jenkins instance without any slaves.

          I'd be happy to provide any other logs, information, or tests required to resolve this issue.
          New: As of version 1.560, polling my private mercurial repository hosted by BitBucket no longer works. Before version 1.560 this worked as expected. Other than Jenkins itself, there were no other changes to the system. The poll configuration looks like:

          H/5 * * * *

          The "poll log" says the following:

          {code}
          Started on Apr 24, 2014 8:08:05 AM
          We need to schedule a new build to get a workspace, but deferring 1,149ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
          Done. Took 1 ms
          No changes
          {code}

          The build does have a valid workspace. Doing a manual build to "get a workspace" does work but does not resolve the polling issue.

          This is a single Jenkins instance without any slaves.

          I'd be happy to provide any other logs, information, or tests required to resolve this issue.

          Jesse Glick added a comment -

          Due to a core change, not Mercurial plugin, so far as I can tell.

          Jesse Glick added a comment - Due to a core change, not Mercurial plugin, so far as I can tell.
          Jesse Glick made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: mercurial [ 15502 ]
          Component/s Original: pollscm [ 17336 ]
          Assignee Original: Jesse Glick [ jglick ]
          Labels New: regression
          Summary Original: Mercurial polling no longer triggers builds (regression 1.560) New: Polling no longer triggers builds (regression 1.560)

          Jesse Glick added a comment -

          Fix of JENKINS-21394 probably introduced this.

          Jesse Glick added a comment - Fix of JENKINS-21394 probably introduced this.
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-21394 [ JENKINS-21394 ]

          Jesse Glick added a comment -

          Note that for Mercurial plugin users, the workaround is likely simple: create a Mercurial installation with the caching option enabled, and use it from your job. That allows non-workspace-based polling, which is more efficient and more reliable. But users of SCM plugins which do not support non-workspace-based polling at all would be out of luck.

          Jesse Glick added a comment - Note that for Mercurial plugin users, the workaround is likely simple: create a Mercurial installation with the caching option enabled, and use it from your job. That allows non-workspace-based polling, which is more efficient and more reliable. But users of SCM plugins which do not support non-workspace-based polling at all would be out of luck.

          Ryan Park added a comment -

          We are also having this problem with triggers from GitHub. We've tried using both the GitHub plugin and the Git plugin. When using the GitHub plugin, we see this error in the GitHub Hook Log:

          Started on Apr 24, 2014 8:42:06 PM
          We need to schedule a new build to get a workspace, but deferring 292ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
          Done. Took 1 ms

          This is a Jenkins system with only one node, the master. The node itself is working fine, and "Refresh Status" works fine on the Manage Nodes page.

          Ryan Park added a comment - We are also having this problem with triggers from GitHub. We've tried using both the GitHub plugin and the Git plugin. When using the GitHub plugin, we see this error in the GitHub Hook Log: Started on Apr 24, 2014 8:42:06 PM We need to schedule a new build to get a workspace, but deferring 292ms in the hope that one will become available soon (all_suitable_nodes_are_offline) Done. Took 1 ms This is a Jenkins system with only one node, the master. The node itself is working fine, and "Refresh Status" works fine on the Manage Nodes page.

          Reto Minder added a comment - - edited

          We use SVN and unfortunately still Clear Case. The Clear Case poll log looks exactly as in the bug description. All svn builds still work properly.

          Reto Minder added a comment - - edited We use SVN and unfortunately still Clear Case. The Clear Case poll log looks exactly as in the bug description. All svn builds still work properly.

            arov Alex Rovner
            jdufresne Jon Dufresne
            Votes:
            43 Vote for this issue
            Watchers:
            75 Start watching this issue

              Created:
              Updated:
              Resolved: