[JENKINS-65922] multi-branch pipeline have the same SVN checkout option as the normal pipeline.

when creating a normal pipeline, if scm is SVN , you can set some checkout option like repository depth, quiet check-out and etc,  like the snapshot below. But when creating a multi branch pipeline, no such options available. The snapshot is attached too.

 

---
Originally reported by caichao1103, imported from: multi-branch pipeline have the same SVN checkout option as the normal pipeline.

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

Raw content of original issue

when creating a normal pipeline, if scm is SVN , you can set some checkout option like repository depth, quiet check-out and etc,  like the snapshot below. But when creating a multi branch pipeline, no such options available. The snapshot is attached too.




 

3 attachments

- [image-2021-06-18-11-04-20-633.png](https://issues.jenkins.io/secure/attachment/55026/image-2021-06-18-11-04-20-633.png)
> 
- [image-2021-06-18-11-04-48-169.png](https://issues.jenkins.io/secure/attachment/55025/image-2021-06-18-11-04-48-169.png)
> 
- [image-2021-06-18-11-06-41-574.png](https://issues.jenkins.io/secure/attachment/55024/image-2021-06-18-11-06-41-574.png)
> 

No source file or test is named. Start by reading the branch-api-plugin multibranch pipeline SCM configuration and comparing it with the normal pipeline SVN checkout options shown in the attachments. Done means multibranch pipelines expose equivalent SVN checkout options, with appropriate coverage added.

Written by the indexing model from the issue text.