[JENKINS-51006] Subversion plugin ignores affected paths for multibranch pipeline trigger

SubversionSCMSource$ListenerImpl onNotify only checks that the UUID of the notification matches the UUID of a SubversionSCMSource instance before telling a multibranch pipeline to execute a branch index. SubversionSCMSource.java#L1043

In the case of a Subversion repo that hosts multiple projects this causes all projects using the same repo to trigger a branch index.

This behavior is inconsistent with what SubversionRepositoryStatus$JobTriggerListenerImpl onNotify does for other job types. SubversionRepositoryStatus.java#L271

---
Originally reported by gjariv, imported from: Subversion plugin ignores affected paths for multibranch pipeline trigger

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

Raw content of original issue

SubversionSCMSource$ListenerImpl onNotify only checks that the UUID of the notification matches the UUID of a SubversionSCMSource instance before telling a multibranch pipeline to execute a branch index. SubversionSCMSource.java#L1043


In the case of a Subversion repo that hosts multiple projects this causes all projects using the same repo to trigger a branch index.


This behavior is inconsistent with what SubversionRepositoryStatus$JobTriggerListenerImpl onNotify does for other job types. SubversionRepositoryStatus.java#L271

environment

```
Jenkins 2.107.2

Subversion-plugin 2.10.5
```