[JENKINS-16469] When using the include region commits to unrelated folders should be masked.

With the git plugin you can set your include regions so that builds are only triggered when a commit comes in on a specific subset of files within the git repo. The problem with this is when builds finally do get triggered in the "changes" section you see all the commits from the unrelated folders as well. As a result of this if the person who made the commit which actually did trigger the build causes an instability then all the people who made unrelated commits in the meantime are spammed with emails that they broke the build when in fact their commit has nothing to do with the actual breakage.

---
Originally reported by scarter, imported from: When using the include region commits to unrelated folders should be masked.

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

Raw content of original issue

With the git plugin you can set your include regions so that builds are only triggered when a commit comes in on a specific subset of files within the git repo.  The problem with this is when builds finally do get triggered in the "changes" section you see all the commits from the unrelated folders as well.  As a result of this if the person who made the commit which actually did trigger the build causes an instability then all the people who made unrelated commits in the meantime are spammed with emails that they broke the build when in fact their commit has nothing to do with the actual breakage.