title: Using a Jenkins pipeline to checkout multiple git repos into same job
body: <p>I'm using the Jenkins Multiple SCM plugin to check out three git repositories into three sub directories in my Jenkins job. I then execute one set of commands to build a single set of artifacts with information and code drawn from all three repositories.</p>
  
  <p>Multiple SCM is now depreciated, and the text recommends moving to pipelines. I tried, but I can't figure out how to make it work.</p>
  
  <p>Here is the directory structure I'm interested in seeing from the top level of my Jenkins job directory:</p>
  
  <pre><code>$ ls
  Combination
  CombinationBuilder
  CombinationResults
  </code></pre>
  
  <p>Each of those three sub-directories has a single git repo checked out. With the Multiple SCM, I used git, and then added the "checkout to a subdirectory" behavior. Here was my attempt with a pipeline script:</p>
  
  <pre><code>node('ATLAS &amp;&amp; Linux') {
      sh('[ -e CalibrationResults ] || mkdir CalibrationResults')
      sh('cd CalibrationResults')
      git url: 'https://github.com/AtlasBID/CalibrationResults.git'
      sh('cd ..')
      sh('[ -e Combination ] || mkdir Combination')
      sh('cd Combination')
      git url: 'https://github.com/AtlasBID/Combination.git'
      sh('cd ..')
      sh('[ -e CombinationBuilder ] || mkdir CombinationBuilder')
      sh('cd CombinationBuilder')
      git url: 'https://github.com/AtlasBID/CombinationBuilder.git'
      sh 'cd ..'
  
      sh('ls')
      sh('. CombinationBuilder/build.sh')
  }
  </code></pre>
  
  <p>However, the git command seems to execute at the top level directory of the workspace (which makes some sense), and according to the syntax too, there doesn't seem to be the checkout-to-sub-directory behavior.</p>