Jenkins World 2016 - Rule Jenkins with Configuration as Code

There are many talks about Jenkins and configuration as code. But how does this work in a real business, on a daily basis? In this session, we will see an example of how to successfully introduce the Job DSL plugin in a real life, medium-size company.

Delivered by Christian Rasp

[omegaldr]

Great presentation Christian! We're doing very similar things with DSL and this is the first time I've ever seen anyone recommend this approach. I did have a question though. Do you end up with 1 seed job that seeds every last build, or 1 seed job that seeds other seed jobs? We started going down the path of having several different seed jobs, but this seems to lengthen the release / distribution cycle and makes it harder to test every build because you don't have access to them from the root seed. Thanks for any info!