[Talk] Migrate Maven CI jobs to Pipeline as code with Jenkins 2 and Docker

This is the talk I gave at DevopsDDay 2016 and Docker Meetup Nantes 2017 about Jenkins 2, Maven, Pipeline as Code and Docker. It was the opportunity to revisit the problems that we have had and the solutions adopted, and some best practices around Maven builds in Docker containers, all managed by the Jenkins Pipeline as Code pattern:

Embedded Video

Recorded @ DevopsDDay 2016

Embedded Slides

Migrate Maven CI jobs to Pipeline as code with Jenkins 2 and Docker from DevopsDDay 2016 & Docker Meetup 2017

Summary of the presentation

Click, click, click… The clicks in the Jenkins UI to handle all the Maven jobs haunt you even at night? You want to manage them with the same process that you use for source code?

If I tell you that you can manage all your Maven builds with 3 lines of Groovy in a Jenkinsfile, it’s cool, isn’it?

exoCI {
    dockerImage = ‘exoplatform/ci:jdk8-maven32’
}

With this case study you will understand why and how we have upgraded more than 300 Jenkins “standard Maven jobs” to Pipelines on our eXo Platform CI instance.
This talk is an opportunity to revisit the problems that we have had and the solutions adopted, and some best practices around Maven builds in Docker containers, all managed by the Jenkins Pipeline as Code pattern.