Continuous Delivery: Pipeline As Code

Bonjour!

Nouvelle session de https://www.eclipsecon.org/france2016/node/2652

Abstract: (descriptif en anglais, mais la session aura bien lieu en français)

If you are using automation tools like Jenkins, you might have found yourself managing a bunch of different jobs: versioning, coordination... You had to install a number of different plugins to handle all that, scattering your configurations across dozens of jobs.

But even when you manage doing all that above: what about maintainability? What happens if the build server reboots in the middle of your sequence of builds? How to have a good visualization of what's currently building? What if you would like to refactor or parallelize some of the steps of the build?

In this session, I'll present the new Jenkins Pipeline Plugin. Actually far more than a single plugin, it was designed to be the foundation onto which a new generation of plugins enabling the so called Continuous Delivery would be built.

Then will walk you through the transformation of an existing (FreeStyle) typical Maven job into a Deployment Pipeline one. From a job described solely in Jenkins, I will show how to move all that code into the project's source code repository and use the Pipeline DSL and show the different ways to define custom reusable DSL steps. We will also explain how to go from a sequential build to a heavily parallelized one, spawning new Jenkins agents on demand on a Docker Swarm cluster.