Trying to implement a Continuous Delivery Pipeline according to the well known book from Jez Humble and David Farley [01] with Jenkins as CI (Continuous Integration) server, everyone stumbeld over following plugins and “technics”
- Build Pipeline Plugin [06]
- Build Flow Plugin [07]
- Delivery Pipeline Plugin [08]
- Parametrized Trigger Plugin [09]
- Job Chaining (up-/downstream)
Possibly you have needed some more.
It was never an easy task whether you used a particular plugin only or a set of them. Every variant of building the pipeline had and has its own pros and cons for sure.
Last year CloudBees Inc. (the company behind Jenkins) announced the “Workflow Engine” [02][03] which should be able to replace all the aforementioned plugins and should make the usage of Jenkins much more developer friendly.
The announcements sound promising, so I decided to give it a try. I would like to invite every one who is interested in this topic to follow my journey in the upcoming blog posts.
References and interesting links:
[01] Jez Humble, David Farley: Continuous Delivery. Addison-Wesley – Copyright 2011 Pearson Education inc. (e.g. via Amazon)
[02] Jenkins Workflow Plugin
[03] Jenkins Workflow Plugin – GitHub-Repo
[04] Jenkins Workflow Screencast
[05] Webinar Orchestrating the CD Process in Jenkins with Workflow
[06] Jenkins Pipeline Plugin
[07] Jenkins Build Flow Plugin
[08] Jenkins Delivery Pipeline Plugin
[09] Jenkins Parametrized Trigger Plugin