[JENKINS-51791] git polling fails to detect changes when build uses multiple repos

I have a Jenkins pipeline job that is configured to trigger builds by polling scm (git) twice a day.  The pipeline job uses a shared library from one repository, and checks out source from three other repositories.  The polling failed to notice new commits on the last three attempts.  I'm attaching the polling log (with the account name and domain expunged).  In addition to missing the new commits in the gvhd2 repo, there's some odd behavior going on here.  It's polling the repo with the shared library in it once, then polling each of the other three repositories 24 times each.  This job uses refs/heads/stable from the shared library repo, and refs/heads/master from the other three.  Since this is a pipeline, there does not appear to be an option to force the polling to use a workspace, which has been suggested as a workaround for these sorts of issues in the past.

---
Originally reported by euphxenos, imported from: git polling fails to detect changes when build uses multiple repos

• status: Open
  
• priority: Major
  
• component(s): git-plugin
  
• resolution: Unresolved
  
• votes: 7
  
• watchers: 8
  
• imported: 2025-12-02
  

Raw content of original issue

I have a Jenkins pipeline job that is configured to trigger builds by polling scm (git) twice a day.  The pipeline job uses a shared library from one repository, and checks out source from three other repositories.  The polling failed to notice new commits on the last three attempts.  I'm attaching the polling log (with the account name and domain expunged).  In addition to missing the new commits in the gvhd2 repo, there's some odd behavior going on here.  It's polling the repo with the shared library in it once, then polling each of the other three repositories 24 times each.  This job uses refs/heads/stable from the shared library repo, and refs/heads/master from the other three.  Since this is a pipeline, there does not appear to be an option to force the polling to use a workspace, which has been suggested as a workaround for these sorts of issues in the past.

• environment: Jenkins 2.107.3 on CentOS 7, git-plugin 3.9.0, the remote git server is Gerrit 2.14.1

1 attachment

- [badpoll](https://issues.jenkins.io/secure/attachment/42807/badpoll)