Continuous Delivery with Jenkins 2

Giorgio Sironi

If you are looking at these slides on your pc, there are speaker notes in the HTML

Giorgio Sironi (@giorgiosironi)

Software Engineer in Test (automates stuff for a living)
What do I do
- Distributed systems
- Automated complex tests, integrating many different projects
- Continuous Delivery
- Pasta and risotto

Classic Jenkins

Just shell scripts

Pipelines

Pipeline as code...

...as a key to automation

Once you have unlocked the pipeline/build logic from inside a tool like Jenkins, which can be unfriendly to developers and the rest of your team, you can the build upon this new layer. For starters, the pipeline is version-controlled. Then, you can make pull requests improving the pipeline and have a colleague review them. Or (totally unrelated), you can have a process automatically discovering all the projects that have a Jenkinsfile and build all their pull requests to give feedback on whether tests are passing. Automation, automation, automation. Moreover, the fact that these pipelines are expressed with a real programming language (Groovy) inside real Git repositories (along with the rest of the code from your projects) makes you able to remove duplication, improving names, and in general do whatever you do to your code to improve it.

Time to work!

http://tinyurl.com/jenkins-cd-workshop a repository providing a turnkey Jenkins
https://github.com/jenkins-cd-workshop a fictional Github user

Conclusions

Representing processes as code not only automates them, but enables a new abstraction layer
Review, clone, refactor your pipelines
Real programming languages get you further than constrained configuration

Thanks!

@giorgiosironi @eLife

g.sironi@elifesciences.org