[JENKINS-42487] Exclude git repository from being polled for changes

Summary

Extension to git-plugin to exclude the specified repository from being polled for changes.

Background

When constructing advanced build-flows with multiple entry points and many involved git repositories via multi-scm, it is sometimes useful to be dependent on a repository for content but not rebuild on changes in that repository.

Using ignore notifyCommit only prevents a polling session from being started but once a poll is done, the repository will still be polled for changes. Hence, a notifyCommit message to a repository (in a multi-scm scenario) that does not have changes (already been built) can still result in a new build due to changes in other repositories configured with ignore notifyCommit.

Also, jobs that use explicit periodic polling will trigger new builds on changes in repositories configured with ignore notifyCommit.

Currently, there is no way of cloning content into workspace using git without polling for changes in all repositories. This feature makes it possible to exclude individual repositories to be polled for changes.

 

---
Originally reported by per_bohlin, imported from: Exclude git repository from being polled for changes

• assignee: per_bohlin
  
• status: In Review
  
• priority: Major
  
• component(s): git-plugin
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 2
  
• imported: 2025-12-02
  

Raw content of original issue

Summary


Extension to git-plugin to exclude the specified repository from being polled for changes.

Background


When constructing advanced build-flows with multiple entry points and many involved git repositories via multi-scm, it is sometimes useful to be dependent on a repository for content but not rebuild on changes in that repository.


Using ignore notifyCommit only prevents a polling session from being started but once a poll is done, the repository will still be polled for changes. Hence, a notifyCommit message to a repository (in a multi-scm scenario) that does not have changes (already been built) can still result in a new build due to changes in other repositories configured with ignore notifyCommit.


Also, jobs that use explicit periodic polling will trigger new builds on changes in repositories configured with ignore notifyCommit.


Currently, there is no way of cloning content into workspace using git without polling for changes in all repositories. This feature makes it possible to exclude individual repositories to be polled for changes.