title: Jenkins-workflow - promotion stage (a better solution than "input")?
body: <p>We started using jenkins-workflow to manage our Continuous Delivery pipeline. </p>
  
  <p>Here is a simple Pipeline example of what we are doing:</p>
  
  <p>[Build project] => [Run unit tests] => [Run integration tests] => [QA Promotion] => [Deploy in QA] => [UAT Promotion] => [Deploy in UAT]</p>
  
  <p>Where:
  [QA Promotion] and [UAT Promotion] are stages waiting for someone to "promote" the build (implemented with the "input" step).</p>
  
  <p>This is purely esthetic, but one thing we found not really nice was that every builds that are waiting at a promotion stage are displayed as "in progress" (with the progress bar indefinitely running). This is weird because if the last 10 builds were not deployed in QA, then we are ending having 10 builds displayed as "running".</p>
  
  <p>I know that waiting for an input will not cause any performance issue. Since if these input steps are not encapsulated inside a node, then they are only consuming flyweight executors (an uncounted slot that is assumed to not take any significant computational power, src: <a href="https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md" rel="noreferrer">https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md</a>).</p>
  
  <p>So, I was wondering if it exists a better solution that would allow us "promoting" builds with the Jenkins Pipeline without the esthetic inconvenience described above.</p>
  
  <p>Thank you</p>