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

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.

---
Originally reported by daniels0xff, imported from: SCM pooling triggers builds one after another and never stops

• status: Open
  
• priority: Critical
  
• component(s): git-plugin
  
• resolution: Unresolved
  
• votes: 5
  
• watchers: 9
  
• imported: 2025-12-02
  

Raw content of original issue

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.

environment

```
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.
```