[JENKINS-24461] Filter change log based on included/excluded regions

When using Included/Excluded regions, allow filtering of the changelog to only commits that match the included/excluded rules.

If a git repo has multiple projects that are built independently, we use included/excluded regions to trigger builds only when changes are made to one of those projects. However, when it does build, it includes commits that affect files outside of that region in the chnagelog. This becomes more of a problem when used in conjunction with Jira issue updating, because a build that is building only component A will add build SUCCESS/FAILURE comments to a Jira issue that is related to component B even though this job did not build component B.

This ticket is like JENKINS-10449 which led to changes supporting this in the SVN components.

---
Originally reported by dgradl, imported from: Filter change log based on included/excluded regions

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

When using Included/Excluded regions, allow filtering of the changelog to only commits that match the included/excluded rules. 


If a git repo has multiple projects that are built independently, we use included/excluded regions to trigger builds only when changes are made to one of those projects.   However, when it does build, it includes commits that affect files outside of that region in the chnagelog.   This becomes more of a problem when used in conjunction with Jira issue updating, because a build that is building only component A will add build SUCCESS/FAILURE comments to a Jira issue that is related to component B even though this job did not build component B.


This ticket is like JENKINS-10449 which led to changes supporting this in the SVN components.