At bol.com we have 70+ applications that are built and supported by 1000+ Jenkins jobs. And that amount is growing by the week. Each set of Continuous Delivery pipelines consists of around 10 jobs which are mostly the same for each application. Maintaining these jobs in Jenkins by hand via the UI is a hell of a job and error-prone at best. What if there was a better way? A way to describe your Continuous Delivery pipelines in code which can be version-controlled, just like your regular code? There is! By using the Jenkins Job DSL plugin and a bit of Groovy scripting. In this code intensive talk you will learn how to significantly mitigate your risk of RSI by distilling your manual job configurations into automated scripts that are readable, easy to maintain and version controlled. tags: Jenkins, Jenkins JobDSL, Groovy

1. Cultivating
the Jenkins job jungle
with Groovy

2. - Jenkins @ bol.com
- Evolution of
Jenkins Management
- Job DSL
- from scratch
- real setup
- Future

3. Jenkins @ bol.com
We have 1085 jobs
Of which, 48 are 'System' jobs
(jobs using System Groovy plugin)
35 scrum teams
97 applications

4. Evolution of
Jenkins Management
- Basic CI
- Multiple jobs per app
- Large with flows
- Continuous Delivery

7. Configuration-as-Code
Don't Repeat Yourself
Version Control

9. Issues
Not managing whole config
May need plugin
May need Jenkins reload

10. JobDSL @ bol.com
From the 1085 jobs we have,
752 are maintained with the JobDSL

11. JobDSL @ bol.com
35 scrum teams

12. Benefits
Consistency
Predictability
Auditability
Self-servicing
No repetitive strain injury (RSI)
Time to do other stuff

13. Future?
Pipeline configuration:
- in project repo
- auto picked up on commit
- run local, in-house, cloud
- no plugins
- takes care of required tools
- IDE support

14. Next-gen Continuous Delivery tool
.cd

15. @pvdissel
github.com/pvdissel/talk-jenkins-jobdsl
Next-gen CD tool? Come help
.cd

16. Images used
- 14766487031_38a4bfcb51_o.jpg
https://www.flickr.com/photos/lukeprice88/14766487031
- 14718610966_07d1039086_o.jpg
https://www.flickr.com/photos/101244975@N08/14718610966
- Jenkins logo
https://wiki.jenkins-ci.org/display/JENKINS/Logo
- 14868422651_35f1ff7e29_o.jpg
https://www.flickr.com/photos/udri/14868422651
- 523336288_2e91d6186d_o.jpg
https://www.flickr.com/photos/guigz/523336288
- continuousDelivery.jpg
http://martinfowler.com/books/continuousDelivery.jpg
- 14936735045_ddb91e2976_o.jpg
https://www.flickr.com/photos/ru_boff/14936735045
- 14766580889_8090d36355_o.jpg
https://www.flickr.com/photos/24337668@N07/14766580889
- 15010592305_009ae3b976_o.jpg
https://www.flickr.com/photos/kurt-b/15010592305
Slide used:
- "Evolution of Jenkins Management"
From "Managing Jenkins With Gradle" by Gary Hale @GradleSummit2014
https://www.youtube.com/watch?v=FGs6_D8ul60
https://speakerdeck.com/ghale/managing-jenkins-with-gradle