[JENKINS-3611] Excluded Regions should be per repository instead of overall

We have some builders with 2 or even 3 repositories to checkout.

One or 2 of them are the main source repositories, and then we have one helper

repository with tooling to which helps the build.

When we enable SVNpolling we like to trigger the build only if there is a change

in the source code repository, not if there is a change in the tooling

repository. If the tooling repository has a change a great number of builders

start running.

To prevent them to start running we can use the 'Excluded Regions' part, but

that is for all repositories instead of repository specific.

For the tooling repository we like to use */.* but if we do that SVN polling

is not working anymore, all repositories are skipped.

Can this feature made per repository?

---
Originally reported by cbos, imported from: Excluded Regions should be per repository instead of overall

• status: Open
  
• priority: Major
  
• component(s): subversion-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 0
  
• imported: 20251212-090250
  

Raw content of original issue

We have some builders with 2 or even 3 repositories to checkout.

One or 2 of them are the main source repositories, and then we have one helper

repository with tooling to which helps the build.


When we enable SVNpolling we like to trigger the build only if there is a change

in the source code repository, not if there is a change in the tooling

repository. If the tooling repository has a change a great number of builders

start running. 

To prevent them to start running we can use the 'Excluded Regions' part, but

that is for all repositories instead of repository specific.

For the tooling repository we like to use */.* but if we do that SVN polling

is not working anymore, all repositories are skipped. 


Can this feature made per repository?

• environment: Platform: All, OS: All