[JENKINS-10922] polling a nonexistent repository disables the job; add setting to control if this should be done or not

the subversion plugin disables the job if it is set to poll for a repository (a branches/ in my case) that does not exist (yet).

It would be convenient if this behavior can be disabled, e.g. by a setting 'Do not disable Job if repository does not exist', because now Jobs are disabled and need to be re-enabled somehow when the branch (or tag or project or...) becomes available.

With this change the Jenkins admin can prepare for projects/branches/... that do not exist yet but will in the near future.

See also JENKINS-10925">JENKINS-10925: parameter substitution on the SVN url does not seem to work when validating the existence of a repository, which, when polling, results in a disabled job too.

---
Originally reported by josbraaksma, imported from: polling a nonexistent repository disables the job; add setting to control if this should be done or not

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

Raw content of original issue

the subversion plugin disables the job if it is set to poll for a repository (a branches/<versionnr> in my case) that does not exist (yet). 


It would be convenient if this behavior can be disabled, e.g. by a setting 'Do not disable Job if repository does not exist', because now Jobs are disabled and need to be re-enabled somehow when the branch (or tag or project or...) becomes available. 

With this change the Jenkins admin can prepare for projects/branches/... that do not exist yet but will in the near future.


See also JENKINS-10925: parameter substitution on the SVN url does not seem to work when validating the existence of a repository, which, when polling, results in a disabled job too.