title: Configure a Jenkins job to select an application and trunk/tags/branches from SVN
body: <p>We want to use a single Jenkins job to build an application.</p>
  
  <p>The solution from <a href="https://stackoverflow.com/q/7751735/2886891">How to configure a single Jenkins job to make the release process from trunk or branches?</a> does <em>not</em> work since <strong>our SVN structure is different</strong> (from historical reasons and we cannot change it):</p>
  
  <pre><code>http://my-svn-repo/projects/
  ├───branches
  │   ├───app1
  │   │   ├───BRANCH_A
  │   │   ├───BRANCH_B
  │   │   └───BRANCH_C
  │   ├───app2
  │   │   ├───BRANCH_D
  │   │   ├───BRANCH_E
  │   │   └───BRANCH_F
  │   └───app3
  │       ├───BRANCH_G
  │       ├───BRANCH_H
  │       └───BRANCH_I
  ├───tags
  │   ├───app1
  │   │   ├───BRANCH_D
  │   │   ├───BRANCH_E
  │   │   └───BRANCH_F
  │   ├───app2
  │   │   ├───TAG_D
  │   │   ├───TAG_E
  │   │   └───TAG_F
  │   └───app3
  │       ├───TAG_G
  │       ├───TAG_H
  │       └───TAG_I
  └───trunk
      ├───app1
      ├───app2
      └───app3
  </code></pre>
  
  <p>The described solution <a href="https://stackoverflow.com/q/7751735/2886891">How to configure a single Jenkins job to make the release process from trunk or branches?</a> shows for selection this:</p>
  
  <ul>
  <li>trunk</li>
  <li>branches/app1</li>
  <li>branches/app2</li>
  <li>branches/app3</li>
  <li>tags/app1</li>
  <li>tags/app2</li>
  <li>tags/app3</li>
  </ul>
  
  <p>What we would like to have is the following:</p>
  
  <p>Selection 1:</p>
  
  <ul>
  <li>app1</li>
  <li>app2</li>
  <li>app3</li>
  </ul>
  
  <p>Selection 2 (automatically based on the selection 1, e.g. for app2):</p>
  
  <ul>
  <li>trunk</li>
  <li>BRANCH_D</li>
  <li>BRANCH_E</li>
  <li>BRANCH_F</li>
  <li>TAG_D</li>
  <li>TAG_E</li>
  <li>TAG_F</li>
  </ul>