[JENKINS-60122] jenkins.branch.WorkpsaceLocatorImpl.MODE=DISABLED does not disable the extension

Hello,

I tried to disable the WorkspaceLocatorImpl by setting the property jenkins.branch.WorkspaceLocatorImpl.MODE to DISABLED

to get a workaround for the issue JENKINS-54776">JENKINS-54776

I assumed that the property disabled the class completely but the WorkspaceCollectorImpl.Collector class still gets called and tries to get a lock on the node which causes the issue JENKINS-54776">JENKINS-54776.

That was not my expected behaviour, I guess that either the property does not work correctly or the javadoc of the property needs some clarification.

---
Originally reported by nirud, imported from: jenkins.branch.WorkpsaceLocatorImpl.MODE=DISABLED does not disable the extension

• status: Open
  
• priority: Minor
  
• component(s): branch-api-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251211-141027
  

Raw content of original issue

Hello,


 I tried to disable the WorkspaceLocatorImpl by setting the property jenkins.branch.WorkspaceLocatorImpl.MODE to DISABLED 

to get a workaround for the issue JENKINS-54776


I assumed that the property disabled the class completely but the WorkspaceCollectorImpl.Collector class still gets called and tries to get a lock on the node which causes the issue JENKINS-54776.


That was not my expected behaviour, I guess that either the property does not work correctly or the javadoc of the property needs some clarification.

environment

```
jenkins version 2.190.2

branch-api 2.5.4
```

Start by reading the jenkins.branch.WorkspaceLocatorImpl.MODE property and the WorkspaceCollectorImpl.Collector entry point mentioned in the report. Reproduce the DISABLED behavior using the reported Jenkins and branch-api versions, then determine whether the property behavior or its Javadoc needs correction; done means the observed behavior matches the documented expectation.

Written by the indexing model from the issue text.