We have several Java projects. Each project has its own delivery pipeline.
All pipelines have the following steps in common (simplified):
- Build project
- Release project
- Deploy to test environment
- Deploy to production environment
The project pipelines only differ in project specific properties such as service names or the IP addresses of test and production environment.
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?
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...