title: How do I chain a manually triggered downstream job, also passing parameters?
body: <p>I am using Jenkins to create a build pipeline, and need to trigger a deployment step in the pipeline. This means a manual process (the build occurs automatically, timed, then stops at the deployment stage, waiting for manual authorization).</p>
  
  <p>I need the deploy step to also be triggered with parameters from the prior step.</p>
  
  <p>So, using the 'Parameterized plugin' I can pass parameters between jobs. I can trigger automated OR manually triggered downstream jobs (not sure if this is a standard feature, or manual builds was added by some plugin). </p>
  
  <p><em>However</em>, I cannot find any way to trigger a manual parameterized job.</p>
  
  <p>Does anyone know of a way to do this? Is there another plugin I can use?</p>
  
  <p>The reason I need the parameters is that I have created a generic deployment job, and need to pass in the module name, and maven version to deploy. I <em>could</em> create specific deployment jobs for each module, but this would be very painful.</p>
  
  <p>I have also been considering the following, but it seems a kludge:</p>
  
  <ol>
  <li>Automated job performs build, triggers 'deployment trigger' build, passing parameters.</li>
  <li>'Deployment trigger' writes these parameters to a file on the filesystem (build step - shell execution), and manually triggers the <em>actual</em> deployment job</li>
  <li>Deployment job (MUST use the WORKSPACE from the 'deployment trigger' job) reads parameters from the filesystem (using EnvInject plugin).</li>
  </ol>
  
  <p>There are various problems with this approach</p>
  
  <ol>
  <li>I just don't like it.</li>
  <li>Has an intermediate jobs <em>just</em> to pass parameters. This clutters the Jenkins workspace</li>
  <li>As builds are performed on the same WORKSPACE, seems fragile to me (though workable!)</li>
  </ol>