[JENKINS-66441] Build Loop from SCM not Updating

[jenkins-infra-bot]

I'm not sure if this is the right plugin, but we've been building what's known as the MOOSE framework for several years with Jenkins without much fuss. Today, I noticed that Jenkins built the same commit like 17 times once per hour (H * * * *) yesterday with Jenkins claiming there was an SCM change, and all of the polling logs look like what's below. The last time I updated the Jenkins version and plugins was also just over a week ago. For whatever reason, it stopped misbehaving on its own, but I'd like to understand what happened here to avoid future build spam.

Started on Aug 22, 2021, 11:59:00 PM
Using strategy: Default
[poll] Last Built Revision: Revision 95b59315a701625070e903eec3a5e37d339aeb42 (refs/remotes/origin/master)
The recommended git tool is: git
No credentials specified
 > git --version # timeout=10
 > git --version # 'git version 2.32.0'
 > git ls-remote -h -- https://github.com/idaholab/moose.git # timeout=10
Found 7 remote heads on https://github.com/idaholab/moose.git
[poll] Latest remote head revision on refs/heads/master is: 1d1b703aef983bb75174883f145cd0d26f10d167
Done. Took 0.18 sec
Changes found

---

Originally reported by herter4171, imported from: Build Loop from SCM not Updating

• status: Open
• priority: Major
• component(s): scm-api-plugin
• resolution: Unresolved
• votes: 0
• watchers: 1
• imported: 20251223-222157

Raw content of original issue

I'm not sure if this is the right plugin, but we've been building what's known as the MOOSE framework for several years with Jenkins without much fuss. Today, I noticed that Jenkins built the same commit like 17 times once per hour (H * * * *) yesterday with Jenkins claiming there was an SCM change, and all of the polling logs look like what's below. The last time I updated the Jenkins version and plugins was also just over a week ago. For whatever reason, it stopped misbehaving on its own, but I'd like to understand what happened here to avoid future build spam.

Started on Aug 22, 2021, 11:59:00 PM
Using strategy: Default
[poll] Last Built Revision: Revision 95b59315a701625070e903eec3a5e37d339aeb42 (refs/remotes/origin/master)
The recommended git tool is: git
No credentials specified
 > git --version # timeout=10
 > git --version # 'git version 2.32.0'
 > git ls-remote -h -- https://github.com/idaholab/moose.git # timeout=10
Found 7 remote heads on https://github.com/idaholab/moose.git
[poll] Latest remote head revision on refs/heads/master is: 1d1b703aef983bb75174883f145cd0d26f10d167
Done. Took 0.18 sec
Changes found

environment

Amazon Linux 2<br/>
openjdk 11.0.11 2021-04-20 LTS<br/>
OpenJDK Runtime Environment 18.9 (build 11.0.11+9-LTS)<br/>
OpenJDK 64-Bit Server VM 18.9 (build 11.0.11+9-LTS, mixed mode, sharing)<br/>
Jenkins 2.303 (non-container, Yum install)<br/>
SCM API 2.6.4

[jenkins-infra-bot]

herter4171:

• Original comment link
• Raw content of original comment:

  This has started happening again for us today.  It's only happens with the MOOSE repo, and all they've done is make a commit in the past 12 hours.  I haven't touched this pipeline setup for at least a year, and I haven't updated Jenkins or its packages in several weeks.  Could I please get some help?  Now that it's happened twice, this is a problem for us.  Thanks.
  

This has started happening again for us today.  It's only happens with the MOOSE repo, and all they've done is make a commit in the past 12 hours.  I haven't touched this pipeline setup for at least a year, and I haven't updated Jenkins or its packages in several weeks.  Could I please get some help?  Now that it's happened twice, this is a problem for us.  Thanks.