title: Jenkins Multi-Pipeline Build Not Detecting Changes in Repository
body: <p>We have a Subversion repository setup in this manor:</p>
  
  <ul>
  <li><code>http://svn.vegicorp.net/svn/toast/api/trunk</code></li>
  <li><code>http://svn.vegicorp.net/svn/toast/api/1.0</code></li>
  <li><code>http://svn.vegicorp.net/svn/toast/data/trunk</code></li>
  <li><code>http://svn.vegicorp.net/svn/toast/data/branches/1.2</code></li>
  <li><code>http://svn.vegicorp.net/svn/toast/data/branches/1.3</code></li>
  </ul>
  
  <p>I've setup a Jenkins Multi-Pipeline build for the entire <em>toast</em> project including all sub-projects -- each sub-project is a jarfile. What I want is for Jenkins to fire off a new build each time any file is changed in one of the toast projects. That project should rebuild. This way, if we create a new sub-project in <em>toast</em> or a new branch in one of the <em>toast</em> sub-projects, Jenkins will automatically create a new build for that.</p>
  
  <p>Here's my Jenkins <em>Multi-Branch</em> setup:</p>
  
  <blockquote>
    <h1>Branch Sources</h1>
    
    <h2>Subversion</h2>
    
    <ul>
    <li><strong>Project Repository Base</strong>: <code>http://svn.vegicorp.net/svn/toast</code></li>
    <li><strong>Credentials</strong>: <code>builder/*****</code></li>
    <li><strong>Include Branches</strong>: <code>*/trunk, */branches/*</code></li>
    <li><strong>Exclude Branches</strong>: <code>*/private</code></li>
    <li><strong>Property Strategy</strong>: <em>All branches get the same properties</em></li>
    </ul>
    
    <h1>Build Configuration</h1>
    
    <ul>
    <li><strong>Mode</strong>: <em>By Jenkinsfile</em></li>
    </ul>
    
    <h1>Build Triggers (<em>None selected</em>)</h1>
    
    <ul>
    <li>Trigger builds remotely (e.g., from scripts)    Help for feature: Trigger * builds remotely (e.g., from scripts)</li>
    <li>Build periodically    Help for feature: Build periodically</li>
    <li>Build when another project is promoted    </li>
    <li>Maven Dependency Update Trigger   Help for feature: Maven Dependency Update Trigger</li>
    <li>Periodically if not otherwise run</li>
    </ul>
  </blockquote>
  
  <p>Note that the list of <em>Build Triggers</em> list does not include <em>Poll SCM</em>. Changes in the repository does not trigger any build. <code>Jenkinsfiles</code> are located at the root of each sub-project. If I force a reindex, all changed sub-projects get built and all new branches are found. I did originally checked <em>Periodically</em> and reindexed every minute to pick up a change, but that's klutzy and it seems to cause Jenkins to consume memory.</p>
  
  <p>Triggering a build on an SCM change should be pretty basic, but I don't see a configuration parameter for this like I do with standard jobs. I also can't seem to go into sub-projects and set those to trigger builds either.</p>
  
  <p>There must be something really, really simple that I am missing.</p>
  
  <p>Configuration:</p>
  
  <ul>
  <li>Jenkins 2.19</li>
  <li>Pipeline 2.3</li>
  <li>Pipeline API: 2.3</li>
  <li>Pipeline Groovy: 2.17</li>
  <li>Pipeline Job: 2.6</li>
  <li>Pipeline REST API Plugin: 2.0</li>
  <li>Pipeline Shared Groovy Libraries: 2.3</li>
  <li>Pipeline: Stage View Plugin: 1.7</li>
  <li>Pipeline: Supporting APIs 2.2</li>
  <li>SCM API Plugin: 1.2</li>
  </ul>