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