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

SCM pooling triggers builds one after another and never stops

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • git-plugin
    • None
    • Jenkins ver. 1.575
      Git plugin Version 2.2.5
      Multiple SCMs plugin 0.3 - configured with 2 GIT sources and @hourly pooling for changes to trigger the build.

      After updating https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin to Version 2.2.5 (Aug 15, 2014) all my jobs that are configured to pull the SCM @hourly started doing builds like crazy one after another even if there were no SCM changes and also having it configured to check @hourly.

      After i downgraded to previous version Version 2.2.4 (Aug 2, 2014), everything is working fine again.

      Maybe this is related to this fix http://issues.jenkins-ci.org/browse/JENKINS-22009

      Stept to reproduce:
      1. Have a build that's already configured and working (Multiple SCMs plugin 0.3 - configured with 2 GIT sources and @hourly pooling for changes to trigger the build)
      2. Update the Git plugin to Version 2.2.5
      3. Go to your working job
      4. Update any setting there (I've just had the branch changed)
      5. Press Apply and start a build. (now Jenkins should start doing builds like crazy one after another always because it was "triggered by a SCM change" where if you go to changes there will be none.

          [JENKINS-24322] SCM pooling triggers builds one after another and never stops

          Try catch Polling log information.

          Kanstantsin Shautsou added a comment - Try catch Polling log information.

          Dane Powell added a comment -

          Dane Powell added a comment - Sounds like https://issues.jenkins-ci.org/browse/JENKINS-25639

          I encountered this trouble and found a solution
          When configuring the branch to build remove the wildcard *:

          */master to be only master
          

          The solution is described here :
          https://stackoverflow.com/questions/30403125/jenkins-build-loop

          Sylvain Mougenot added a comment - I encountered this trouble and found a solution When configuring the branch to build remove the wildcard *: */master to be only master The solution is described here : https://stackoverflow.com/questions/30403125/jenkins-build-loop

            Unassigned Unassigned
            daniels0xff Daniel Anechitoaie
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: