Declarative pipeline syntax in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a declarative Jenkins pipeline.

Jenkins

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

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

Adocker

Bnode

Cmaster

Dany

Attempts:

3 left

💡 Hint

Common Mistakes

Using node which is scripted pipeline syntax.

Using master which is deprecated.

Using docker without proper configuration.

The agent any directive tells Jenkins to run the pipeline on any available agent.

2fill in blank

medium

Complete the code to define a stage named 'Test'.

Jenkins

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

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

A'Deploy'

B'Build'

C'Test'

D'Verify'

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the stage name.

Using the wrong stage name.

The stage name is given as a string. Here, the stage is named 'Test'.

3fill in blank

hard

Fix the error in the steps block to print 'Deploying...'.

Jenkins

pipeline {
    agent any
    stages {
        stage('Deploy') {
            steps {
                [1] 'Deploying...'
            }
        }
    }
}

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

Awrite

Becho

Cprintln

Dprint

Attempts:

3 left

💡 Hint

Common Mistakes

Using print which is not recognized in Jenkins pipelines.

Using println which is not valid here.

In Jenkins declarative pipelines, echo is used to print messages to the console.

4fill in blank

hard

Fill both blanks to add a post action that always runs and echoes 'Cleaning up'.

Jenkins

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

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

Aalways

Becho

Csuccess

Dfailure

Attempts:

3 left

💡 Hint

Common Mistakes

Using success or failure instead of always.

Using print instead of echo.

The post section can have conditions like always to run steps regardless of build result. Inside it, echo prints the message.

5fill in blank

hard

Fill all three blanks to create an environment variable named 'VERSION' with value '1.0' and echo it in the build stage.

Jenkins

pipeline {
    agent any
    environment {
        [1] = [2]
    }
    stages {
        stage('Build') {
            steps {
                [3] "Version is $VERSION"
            }
        }
    }
}

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

AVERSION

B"1.0"

Cecho

Dversion

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase variable names.

Not quoting the value string.

Using print instead of echo.

Environment variables are declared with a name and value. Here, VERSION is set to "1.0". Then echo prints the message using the variable.

Practice

1. Which block is mandatory to start a Jenkins declarative pipeline?

easy

A. stage

B. agent

C. steps

D. pipeline

Solution

1. Step 1: Understand the pipeline structure

   The pipeline block is the root block that wraps the entire declarative pipeline script.

2. Step 2: Identify mandatory blocks

   While agent, stages, and steps are important, the pipeline block is always required to define the pipeline.

3. Final Answer:

   <code>pipeline</code> -> Option D

4. Quick Check:

   Root block = pipeline [OK]

Hint: Look for the root block that wraps everything [OK]

Common Mistakes:

• Confusing stage as root block
• Thinking steps is the top block
• Assuming agent is mandatory alone

2. Which of the following is the correct syntax to define an agent that runs on any available node?

easy

A. agent any

B. agent: any

C. agent { any }

D. agent = any

Solution

1. Step 1: Recall agent syntax in declarative pipeline

   The correct syntax to specify an agent that runs on any available node is agent any without punctuation.

2. Step 2: Check other options for syntax errors

   Options with colons, braces, or equals signs are invalid in declarative pipeline syntax for agent.

3. Final Answer:

   agent any -> Option A

4. Quick Check:

   Agent syntax is simple: agent any [OK]

Hint: Remember: no punctuation, just 'agent any' [OK]

Common Mistakes:

• Adding colons or braces around 'any'
• Using equals sign instead of space
• Confusing scripted pipeline syntax

3. What will be the output of this Jenkins declarative pipeline snippet?

pipeline {
  agent any
  stages {
    stage('Hello') {
      steps {
        echo 'Hello World'
      }
    }
  }
}

medium

A. Fails because 'echo' is not allowed in declarative pipeline

B. Prints 'Hello World' in the build log

C. Pipeline runs but no output is shown

D. Syntax error due to missing agent label

Solution

1. Step 1: Analyze the pipeline structure

   The pipeline has a valid agent any, one stage named 'Hello', and a step that echoes 'Hello World'.

2. Step 2: Understand the echo step behavior

   The echo step prints the given message to the Jenkins build log during execution.

3. Final Answer:

   Prints 'Hello World' in the build log -> Option B

4. Quick Check:

   echo prints message to log [OK]

Hint: echo always prints text to Jenkins console [OK]

Common Mistakes:

• Thinking echo is disallowed in declarative pipelines
• Assuming missing agent label causes error here
• Believing pipeline runs silently without output

4. Identify the error in this declarative pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'make build'
      }
    }
  }
  steps {
    echo 'Done'
  }
}

medium

A. The sh command is invalid in declarative pipeline

B. Missing agent block

C. The steps block is misplaced outside stage

D. The stage block must be outside stages

Solution

1. Step 1: Review pipeline block structure

   In declarative pipelines, steps must be inside a stage block, which is inside stages.

2. Step 2: Locate the misplaced steps block

   The steps block with echo 'Done' is incorrectly placed directly under pipeline, outside any stage.

3. Final Answer:

   The <code>steps</code> block is misplaced outside <code>stage</code> -> Option C

4. Quick Check:

   steps must be inside stage [OK]

Hint: steps always go inside a stage block [OK]

Common Mistakes:

• Placing steps directly under pipeline
• Confusing agent placement
• Thinking sh is invalid in declarative pipelines

5. You want to run two stages in parallel in a declarative pipeline. Which snippet correctly defines parallel stages?

hard

A. pipeline {
agent any
stages {
stage('Parallel') {
parallel {
stage('Test') {
steps { echo 'Testing' }
}
stage('Build') {
steps { echo 'Building' }
}
}
}
}
}

B. pipeline {
agent any
stages {
parallel {
stage('Test') {
steps { echo 'Testing' }
}
stage('Build') {
steps { echo 'Building' }
}
}
}
}

C. pipeline {
agent any
stages {
stage('Test') {
steps { echo 'Testing' }
}
stage('Build') {
steps { echo 'Building' }
}
}
}

D. pipeline {
agent any
parallel {
stage('Test') {
steps { echo 'Testing' }
}
stage('Build') {
steps { echo 'Building' }
}
}
}

Solution

1. Step 1: Understand parallel syntax in declarative pipeline

   Parallel stages must be nested inside a stage block using the parallel block.

2. Step 2: Check each option for correct structure

   pipeline {
     agent any
     stages {
       stage('Parallel') {
         parallel {
           stage('Test') {
             steps { echo 'Testing' }
           }
           stage('Build') {
             steps { echo 'Building' }
           }
         }
       }
     }
   }

   correctly places parallel inside a stage named 'Parallel' with nested stages 'Test' and 'Build'. Other options place parallel incorrectly or omit it.

3. Final Answer:

   Option A with parallel inside a stage block -> Option A

4. Quick Check:

   parallel inside stage block = correct [OK]

Hint: Parallel block must be inside a stage block [OK]

Common Mistakes:

• Placing parallel directly under stages
• Omitting the parallel block
• Placing parallel outside pipeline