What is job-dsl-plugin?
Job DSL was one of the first popular plugins for Jenkins which allows managing configuration as code and many other plugins dealing with this aspect have been created since then, most notably the Jenkins Pipeline and Configuration as Code plugins. It is important to understand the differences between these plugins and Job DSL for managing Jenkins configuration efficiently.
How to make a seed pipeline to seed other pipeline?
Scenario 1: Create a pipeline job manually
- Step 1: Create a new repo with Jenkinsfile
// file: Jenkinsfile
// repo: sample-scripted-pipeline
node {
echo "It's a sampe scripted pipeline" }
- Step 2: Create a new
pipelinebase on previous repo manually
Goto the
./job/pipleine-test-script/config.xmlto check the xml config.
<flow-definition plugin="[email protected]">
<actions/> <description/> <keepDependencies>false</keepDependencies> <properties> <hudson.plugins.jira.JiraProjectProperty plugin="[email protected]"/> </properties> <definition class="org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition" plugin="[email protected]"> <scm class="hudson.plugins.git.GitSCM" plugin="[email protected]"> <configVersion>2</configVersion> <userRemoteConfigs> <hudson.plugins.git.UserRemoteConfig> <url>https://github.com/geekchow/sample-scripted-pipeline.git</url> <credentialsId>token-for-github</credentialsId> </hudson.plugins.git.UserRemoteConfig> </userRemoteConfigs> <branches> <hudson.plugins.git.BranchSpec> <name>*/master</name> </hudson.plugins.git.BranchSpec> </branches> <doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations> <submoduleCfg class="list"/> <extensions/> </scm> <scriptPath>Jenkinsfile</scriptPath> <lightweight>true</lightweight> </definition> <triggers/> <disabled>false</disabled> </flow-definition>
Scenario 2: Create pipeline from a seed pipeline: sample-seed-pipeline with scriptText approach
- Step 1: Create seed pipeline
// file: Jenkinsfile
def jobDefinition = '''
pipelineJob('sample-child-pipeline') { definition { cpsScm { scm { git { remote { url('https://github.com/geekchow/sample-scripted-pipeline.git') credentials('token-for-github') } branch('*/master') } } scriptPath('Jenkinsfile') lightweight() } } } ''' node('master') { step([ $class: 'ExecuteDslScripts', scriptText: jobDefinition, lookupStrategy: 'SEED_JOB' ]) }
To make the dsl pipeline definition readable we could seperate the job Definition into a groovy file.
// file: Jenkinsfile
node('master') {
checkout(scm)
step([
$class: 'ExecuteDslScripts', targets: 'SeedPipeline.groovy', lookupStrategy: 'SEED_JOB' ]) }
// file: SeedPipeline.groovy
pipelineJob('sample-child-pipeline') {
definition {
cpsScm {
scm {
git {
remote {
url('https://github.com/geekchow/sample-scripted-pipeline.git') credentials('token-for-github') } branch('*/master') } } scriptPath('Jenkinsfile') lightweight() } } }
- Step 2: Run seed pipeline to fork a new pipeline The new pipeline
sample-child-pipelinewas created by the sample seed pipeline.
Source code: https://github.com/geekchow/sample-seed-pipeline.git