Scripted vs declarative comparison in Jenkins - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a declarative Jenkins pipeline.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                [1] 'echo Building...'
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

Astage

Bscript

Cnode

Dsh

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'script' instead of 'sh' inside steps.

In declarative pipelines, sh is used to run shell commands inside steps.

2fill in blank

medium

Complete the code to define a scripted Jenkins pipeline node block.

Jenkins

node {
    stage('Test') {
        [1] 'echo Testing...'
    }
}

Drag options to blanks, or click blank then click option'

Ash

Bpipeline

Csteps

Dagent

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'steps' which is not valid in scripted pipeline.

In scripted pipelines, sh runs shell commands inside the node block.

3fill in blank

hard

Fix the error in the scripted pipeline to properly wrap shell commands.

Jenkins

node {
    stage('Deploy') {
        [1] {
            sh 'echo Deploying...'
        }
    }
}

Drag options to blanks, or click blank then click option'

Ascript

Bsteps

Cpipeline

Dagent

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'steps' which is only valid in declarative pipelines.

In scripted pipelines, script block is used to wrap multiple steps or commands.

4fill in blank

hard

Fill both blanks to create a declarative pipeline with a post action.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh 'echo Building...'
            }
        }
    }
    post {
        [1] {
            [2] 'echo Cleaning up...'
        }
    }
}

Drag options to blanks, or click blank then click option'

Aalways

Bsh

Csuccess

Dscript

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'script' in post steps which is invalid.

The post section uses conditions like always to run steps such as sh commands after the pipeline.

5fill in blank

hard

Fill all three blanks to create a scripted pipeline with a stage and shell command.

Jenkins

node {
    stage('[1]') {
        [2] '[3]'
    }
}

Drag options to blanks, or click blank then click option'

ADeploy

Bsh

Cecho Deploying...

DBuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Build' instead of 'Deploy' for the stage name.

The stage name is 'Deploy', the shell command is run with sh, and the command string is 'echo Deploying...'.

Practice

1. Which statement best describes the main difference between scripted and declarative Jenkins pipelines?

easy

A. Scripted pipelines use Groovy code and are flexible; declarative pipelines have a fixed structure and are easier to read.

B. Declarative pipelines use Groovy code and are flexible; scripted pipelines have a fixed structure and are easier to read.

C. Both scripted and declarative pipelines have the same syntax and flexibility.

D. Scripted pipelines are only for building Java projects; declarative pipelines are for all other projects.

Solution

1. Step 1: Understand scripted pipeline nature

   Scripted pipelines use Groovy code, allowing more flexibility but requiring more coding skill.

2. Step 2: Understand declarative pipeline nature

   Declarative pipelines have a fixed, simpler structure designed for easier writing and reading.

3. Final Answer:

   Scripted pipelines use Groovy code and are flexible; declarative pipelines have a fixed structure and are easier to read. -> Option A

4. Quick Check:

   Scripted = flexible Groovy, Declarative = fixed structure [OK]

Hint: Remember: scripted = flexible code, declarative = fixed format [OK]

Common Mistakes:

• Confusing which pipeline uses Groovy code
• Thinking both pipelines have the same syntax
• Believing scripted pipelines are only for Java

2. Which of the following is the correct way to start a declarative Jenkins pipeline script?

easy

A. node { stage('Build') { echo 'Building...' } }

B. def build() { echo 'Building...' }

C. build { echo 'Building...' }

D. pipeline { agent any; stages { stage('Build') { steps { echo 'Building...' } } } }

Solution

1. Step 1: Identify declarative pipeline syntax

   Declarative pipelines start with the pipeline {} block and include agent and stages.

2. Step 2: Compare options

   pipeline { agent any; stages { stage('Build') { steps { echo 'Building...' } } } } correctly uses pipeline { agent any; stages { stage('Build') { steps { echo 'Building...' } } } } which matches declarative syntax.

3. Final Answer:

   pipeline { agent any; stages { stage('Build') { steps { echo 'Building...' } } } } -> Option D

4. Quick Check:

   Declarative starts with pipeline block [OK]

Hint: Declarative pipelines always start with 'pipeline { ... }' [OK]

Common Mistakes:

• Using scripted syntax for declarative pipelines
• Omitting the 'pipeline' block
• Missing 'stages' or 'steps' keywords

3. Given this scripted pipeline snippet, what will be the output?

node {
  stage('Test') {
    echo 'Running tests'
  }
}

medium

A. Prints 'Running tests' during the 'Test' stage

B. Syntax error because 'stage' is not allowed in scripted pipelines

C. No output because 'node' block is empty

D. Pipeline fails due to missing 'pipeline' block

Solution

1. Step 1: Analyze scripted pipeline structure

   The scripted pipeline uses node and stage blocks correctly with an echo step inside.

2. Step 2: Determine output

   The pipeline will run the 'Test' stage and print 'Running tests' to the console.

3. Final Answer:

   Prints 'Running tests' during the 'Test' stage -> Option A

4. Quick Check:

   Scripted pipelines allow stage and echo inside node [OK]

Hint: Scripted pipelines use node and stage blocks freely [OK]

Common Mistakes:

• Thinking 'stage' is only for declarative pipelines
• Expecting a syntax error without 'pipeline' block
• Assuming no output if node block is present

4. Identify the error in this declarative pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      echo 'Building...'
    }
  }
}

medium

A. Incorrect use of 'pipeline' keyword

B. Missing 'agent' declaration

C. Missing 'steps' block inside the 'Build' stage

D. Using 'echo' instead of 'sh' command

Solution

1. Step 1: Review declarative pipeline stage structure

   Each stage must contain a steps block that holds the commands to run.

2. Step 2: Check the snippet

   The 'Build' stage directly contains echo without wrapping it inside steps {}, which is invalid.

3. Final Answer:

   Missing 'steps' block inside the 'Build' stage -> Option C

4. Quick Check:

   Declarative stages require steps block [OK]

Hint: Declarative stages always need a 'steps' block [OK]

Common Mistakes:

• Omitting the 'steps' block inside stages
• Confusing scripted and declarative syntax
• Thinking 'echo' must be replaced by 'sh'

5. You want to create a Jenkins pipeline that runs a complex Groovy script for dynamic branching but also wants to keep some stages simple and readable. Which approach is best?

hard

A. Use a fully scripted pipeline for all stages to keep consistency.

B. Use a declarative pipeline with a scripted block inside for complex parts.

C. Use only declarative pipeline and avoid any Groovy scripting.

D. Write two separate pipelines and run them manually.

Solution

1. Step 1: Understand pipeline flexibility needs

   Complex dynamic branching requires Groovy scripting flexibility, which scripted pipelines provide.

2. Step 2: Combine declarative simplicity with scripted flexibility

   Declarative pipelines allow embedding scripted blocks for advanced logic, keeping most stages simple and readable.

3. Final Answer:

   Use a declarative pipeline with a scripted block inside for complex parts. -> Option B

4. Quick Check:

   Declarative + scripted block = best of both worlds [OK]

Hint: Embed scripted blocks inside declarative for complex logic [OK]

Common Mistakes:

• Using only scripted pipeline losing readability
• Avoiding scripted blocks in declarative pipelines
• Running separate pipelines manually instead of combining