Declarative pipeline syntax in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a simple Declarative Pipeline

What will be the output of the following Jenkins Declarative Pipeline when run?

Jenkins

pipeline {
  agent any
  stages {
    stage('Example') {
      steps {
        echo 'Hello, Jenkins!'
      }
    }
  }
}

A Console shows: Hello, Jenkins!

B Build fails with syntax error

C Pipeline runs but no output is shown

D Build is skipped automatically

💡 Hint

Look at the echo step inside the stage.

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

❓ Configuration

intermediate

Correct agent declaration in Declarative Pipeline

Which option correctly declares an agent that runs on any available node in a Jenkins Declarative Pipeline?

A agent any

B agent none

C agent label 'any'

D agent node

💡 Hint

The keyword for any available node is a simple word.

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

🔀 Workflow

advanced

Stage execution order in Declarative Pipeline

Given this Declarative Pipeline, in what order will the stages execute?

Jenkins

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

A Build, Deploy, Test

B Deploy, Test, Build

C Test, Build, Deploy

D Build, Test, Deploy

💡 Hint

Stages run in the order they are defined.

Declarative Pipeline stages run sequentially in the order they appear in the Jenkinsfile.

❓ Troubleshoot

advanced

Error caused by missing steps block

What error will Jenkins show if a stage in a Declarative Pipeline is missing the required steps block?

Jenkins

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

A No error, pipeline runs fine

B Runtime error: 'echo' command not found

C Syntax error: Expected a steps block inside stage

D Warning: Missing steps block, but pipeline continues

💡 Hint

Declarative Pipeline requires steps inside stages.

Each stage must have a steps block; missing it causes a syntax error.

✅ Best Practice

expert

Proper use of post section in Declarative Pipeline

Which option correctly uses the post section to always run a cleanup step after all stages, regardless of build result?

A

post {
  success {
    echo 'Cleaning up...'
  }
}

B

post {
  always {
    echo 'Cleaning up...'
  }
}

C

post {
  failure {
    echo 'Cleaning up...'
  }
}

D

post {
  changed {
    echo 'Cleaning up...'
  }
}

💡 Hint

You want the cleanup to run no matter what happens.

The 'always' condition in post runs the steps regardless of build success or failure.