Automating Job Configurations with Jenkins Job DSL

Jenkins is the heart of CI/CD processes.
However, creating jobs manually one by one is time-consuming and error-prone.

The modern DevOps approach says Everything as Code.
Job DSL provides exactly that.

In this guide, you will learn how to code Jenkins jobs with Groovy-based DSL.

Technical Summary

This guide covers automating job configurations with the Jenkins Job DSL plugin.
The goal is to manage job definitions as code and eliminate manual processes.

The flow is as follows:

• Job DSL plugin is installed
• Seed Job is created
• Jobs are produced automatically by running DSL script

---

What Will You Learn in This Guide?

• Installing the Job DSL plugin
• Understanding Seed Job logic
• Producing freestyle jobs with code
• Creating GitHub based Pipeline job
• Making Jenkins jobs versionable

---

Prerequisites

• A Jenkins server with administrative privileges
• Basic command of the Jenkins interface
• Knowing Groovy is an advantage

---

1. Installing Job DSL Plugin

Job DSL allows you to define Jenkins jobs with code.

Path:

• Manage Jenkins → Manage Plugins
• Available tab
• Job DSL → Install without restart

When the installation is complete, you should see Success.

---

2. Seed Job Creation

Seed Job is the main job that creates other jobs.
It runs the DSL script and produces Jenkins jobs.

Sample Job DSL Script

job('demo-is') {
    steps {
        shell('echo Merhaba Dunya!')
    }
}

---

Description:

• This script creates a freestyle job called demo-is.

Seed Job Setup

1. ew Item → Freestyle Project

2. Name: seed-job

3. Build Step → Process Job DSLs

4. Use the provided DSL script

5. Paste the script → Save

---

3. Running a Seed Job

# Jenkins arayüzünden Build Now seçilir

Result:

Demo-is appears under -Generated Items

When demo-is is run, Hello World! appears on the console.

---

4. Pipeline Job Definition

1. Pipeline job is used in real projects. Job DSL supports this too.

---

Required Plugins

1. Go

2. Pipeline: Job

3. Pipeline: Groovy

Advanced Job DSL Script

job('demo-is') {
    steps {
        shell('echo Merhaba Dunya!')
    }
}

pipelineJob('github-demo-pipeline') {
    definition {
        cpsScm {
            scm {
                git {
                    remote {
                        github('jenkinsci/pipeline-examples')
                    }
                }
            }
            scriptPath(
              'declarative-examples/simple-examples/environmentInStage.groovy'
            )
        }
    }
}

---

Description:

• This script creates a job that pulls pipelines from GitHub. When the Seed Job is run again, the new job is added automatically.

---

Frequently Asked Questions (FAQ)

1. Why is Job DSL important? It allows you to manage Jenkins jobs with code.

2. If the Seed Job is deleted, will the jobs be deleted? No. But management disappears.

3. Where should DSL scripts be kept? It is best practice to keep them in a Git repository.

4. Can hundreds of jobs be managed with Job DSL? Yes. Ideal for large-scale Jenkins builds.

---

Result

Congratulations, you have defined your Jenkins jobs as code.

Thanks to Job DSL:

1.Repeatable

2. Versionable

3. You can install portable Jenkins builds

You can use GenixNode VDS solutions with peace of mind to run this automation on a high-performance infrastructure.