bug #7579
Updated by Andreas Kohlbecker about 3 years ago
Our jenkins setup are using the [build-pipeline-plugin](https://plugins.jenkins.io/build-pipeline-plugin). Since Jenkins 2 there is a much better tool to setup pipelines, [Jenkins Pipeline](https://jenkins.io/doc/book/pipeline/) see the following resources for information on how to use it: * https://jaxenter.de/pipeline-jenkins-2-61568 * https://jenkins.io/doc/book/pipeline/ (see also the links in the paragraph: "Die „Top 10 Best Practices for Jenkins Pipeline Plugin„, die „Best Practices for Scalable Pipeline Code“ und „The Need For Speed: Building Pipelines To Be Faster„. Hier finden sich allgemeine Best Practices sowie wichtige Hinweise zur Entwicklung performanter, ") * https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md --- Jenkinsfile should be used: Creating a [Jenkinsfile](https://www.jenkins.io/doc/book/pipeline/jenkinsfile/) and committing it to source control provides a number of immediate benefits: * Automatically creates a Pipeline **build process for all branches and pull requests.** * Code review/iteration on the Pipeline (along with the remaining source code). * Audit trail for the Pipeline. * Single source of truth [3] for the Pipeline, which can be viewed and edited by multiple members of the project.