title: Jenkins pipeline template
body: <p>We have several Java projects. Each project has its own delivery pipeline.</p>
  
  <p>All pipelines have the following steps in common (simplified):</p>
  
  <ul>
  <li>Build project</li>
  <li>Release project</li>
  <li>Deploy to test environment</li>
  <li>Deploy to production environment</li>
  </ul>
  
  <p>The project pipelines only differ in project specific properties such as service names or the IP addresses of test and production environment.</p>
  
  <p>The questions are: How could we avoid the boilerplate that all projects have in common? Does Jenkins "Pipeline as code" provide something like pipeline templates?</p>
  
  <p>I could imagine that a template would save a lot of redundant code/steps in our project pipelines. Therefore it would be much easier to setup a new project, maintain the pipeline, keep the pipeline in sync...</p>