Out of the box Jenkins supports only the XML-based configuration files. This makes it difficult not only to introduce changes, but also to review and test them properly.
After relying for a long time on the manual Jenkins configuration, we decided to improve our setup and introduce proper workflow for automated deployment/recovery after an outage and testing for any new change in Jenkins configuration. We selected recent Configuration-as-a-Code plugin, Job DSL with Pipelines mechanism to achieve the goal.
The attenders will learn about Jenkins Configuration-as-a-Code plugin and Job DSL along with their capabilities when combined together with Pipelines mechanism. We will also discuss how it is possible to test the Jenkins configuration and keep it in a code-review system.