title: Multibranch Pipeline in Jenkins with SVN
body: <p>I have SVN as my SCM. The SVN Root URL structure is as follows.
  <a href="https://svn.domain.com/orgName" rel="nofollow noreferrer">https://svn.domain.com/orgName</a></p>
  <p>Under this, I have a folder called &quot;test&quot;. Then I have tags, branches and trunk. For example,
  <a href="https://svn.domain.com/orgName/test/trunk" rel="nofollow noreferrer">https://svn.domain.com/orgName/test/trunk</a><br />
  <a href="https://svn.domain.com/orgName/test/branches" rel="nofollow noreferrer">https://svn.domain.com/orgName/test/branches</a></p>
  <p>Under trunk and branches, I have various modules. One module is Platform which is the core module. The URL structure for my project under Platform is as follows.</p>
  <p><a href="https://svn.domain.com/orgName/test/trunk/Platform/MyProject" rel="nofollow noreferrer">https://svn.domain.com/orgName/test/trunk/Platform/MyProject</a>
  <a href="https://svn.domain.com/orgName/test/branches/Platform/1.0.0.0/MyProject" rel="nofollow noreferrer">https://svn.domain.com/orgName/test/branches/Platform/1.0.0.0/MyProject</a></p>
  <p>Not sure if the above structure is correct or not. But this is how it is structured in my organization and it can't be changed. Now, I have the following questions.</p>
  <ol>
  <li>At what level should I maintain the Jenkinsfile?</li>
  <li>How should I pass the branch name (including trunk) to this file?</li>
  </ol>
  <p>It will be great if someone can provide some details (if possible step by step) on how to use Multibranch pipeline with SVN. Unfortunately, I could not find any tutorial or examples to achieve this.</p>