title: How to build a pipeline of jobs in Jenkins?
body: <p>In my project, I have 3 web-applications, all depend on one <code>all-commons</code> project.</p>
  
  <p>In my Jenkins server, I built 4 jobs, <code>all-commons_RELEASE</code>, <code>web-A_RELEASE</code>, <code>web-B_RELEASE</code> and <code>web-C_RELEASE</code>. 
  The role of these jobs is to build the artifacts, which are deployed on our Nexus. Then, someone retrieve these artifacts in Nexus and deploy them on our dev / homologation servers.</p>
  
  <p>What I want, is to have one (additional?) job that will launch all the 4 builds, in a sequential way.
  This way, once this job is finished, all the RELEASE jobs have been executed.
  Of course, if one build fails, the process is stopped.</p>
  
  <p>My first thought was to indicate the <code>web-A_RELEASE</code> in the <em>Build other projects</em> list of the <em>Post-build Actions</em> of <code>all-commons_RELEASE</code>.
  Then, <code>web-B_RELEASE</code> is dependent on <code>web-A_RELEASE</code>, and so on.</p>
  
  <p>However, I want to be able to start any of them separately, which is not possible if I indicate a dependency on the projects. For example, if I manually start <code>web-B_RELEASE</code>, then <code>web-C_RELEASE</code> will be built after that, which is not what I want...</p>
  
  <p>Do you have any idea how I can achieve that, or a plugin to help me to do that?</p>
  
  <p>Regards.</p>
  
  <p>ps: Jenkins 1.430, and all RELEASE jobs are free-style projects (they mix Maven and bash commands).</p>