This will be moved to the new website pending WEBSITE-51
The default interaction model with Jenkins, historically, has been very web UI driven, requiring users to manually create jobs, then manually fill in the details through a web browser. This requires additional effort to create and manage jobs to test and build multiple projects, it also keeps the configuration of a job to build/test/deploy separate from the actual code being built/tested/deployed. This prevents users from applying their existing CI/CD best practices to the job configurations themselves.
With the introduction of the Pipeline Plugin, users now can implement a project's entire build/test/deploy pipeline in a
Jenkinsfile and store that alongside their code, treating their pipeline as another piece of code checked into source control.
- The Pipeline Plugin has this, fairly comprehensive, tutorial checked into its source tree.
- Overview of Continuous Delivery with Workflow
- DZone Refcard
- Pipeline as code "cook book"
- Pipeline Plugin page
- Plugins compatible with Pipeline
- Stack Overflow "jenkins-workflow" tag
- Examples repository