Many people uses Jenkins for testing changes in their software automatically. But do as many people tests changes in Jenkins itself?
Utilization of Jenkins Configuration as Code plugin, Job DSL and Pipelines mechanism allows one to store configuration in a programer-friendly way. As a consequence, it makes it easier to introduce proper workflow with review of changes. However, as compulsory part such review process shall contain the non-interactive, automated tests.
During this presentation we would like to cover the topic of such verification. On our own example we discuss not only basic syntax checking, but also the idea of more sophisticated scenario/integration tests with different services, like Gerrit.
The attenders will learn how they can test their Jenkins configuration. We will propose useful tools and how to involve them in advanced verification of Jenkins integration with utilized services like Gerrit.