The 3rd part of the Jenkins-as-Code series focuses on the automated creation of job interfaces. That could be achieved with pure groovy scripting as used in the previous part. However, the JobDSL plugin offers a more convenient and clean way, so we will focus on that.
There are already quite a lot of tutorials and code snippets about the JobDSL plugin all over the web, so this will be a rather short post. I post this merely for the sake of completion as without JobDSL, Jenkins is not fully as-code.
JobDSL is a DSL language on top of groovy. It offers an easy way to describe job interfaces as-code. It is very common to have a job interface seeding pipeline, which pulls the jobDSL code from a repository and provisions the job interfaces. Jenkins jobDSL is very easy to understand and write. It is easy to pickup as it comes with a good documentation. However, jobDSL can only provision features of plugins that are already installed in your jenkins instance. So the online documentation might show you features which are not available to your jenkins instance because of missing plugins. You can find all available features documented on your jenkins instance at
Further, there is an online playground for jobDSL scripts. It translates your scripts to the final xml of the job interface, so it is ideal to quickly validate your scripts during jobDSL development.
Multibranch Build Pipelines
After all that praise, now let’s have a look at some code. In the following we create a set of Multibranch Pipelines for project repositories on Github:
We assume that Jenkins is already hooked up with Github, which is a requirement for a Github Multibranch pipeline to function.
A seed pipeline to trigger the jobDSL could look like that:
This short post gave a quick overview of the JobDSL plugin and how to use it. We created a simple DSL for multibranch pipeline job interfaces of different projects hosted on Github.