Steps within stages in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of multiple steps in a Jenkins stage

Consider the following Jenkins pipeline stage snippet. What will be the output in the Jenkins console when this stage runs?

Jenkins

stage('Build') {
  steps {
    echo 'Step 1: Compile'
    echo 'Step 2: Test'
    echo 'Step 3: Package'
  }
}

A Step 1: Compile Step 2: Test Step 3: Package

B Step 1: Compile\nStep 2: Test\nStep 3: Package

C Step 3: Package\nStep 2: Test\nStep 1: Compile

D No output is produced

💡 Hint

Remember Jenkins runs steps in the order they are written inside the stage.

Jenkins executes steps sequentially inside a stage. Each echo prints its message on a new line in the console output.

❓ Configuration

intermediate

Correct syntax for multiple steps in a Jenkins stage

Which of the following Jenkins pipeline stage configurations correctly defines multiple steps inside a stage?

A

stage('Deploy') {
  steps {
    sh 'deploy.sh'
    echo 'Deployment complete'
  }
}

B

stage('Deploy') {
  sh 'deploy.sh'
  echo 'Deployment complete'
}

C

stage('Deploy') {
  steps: [sh 'deploy.sh', echo 'Deployment complete']
}

D

stage('Deploy') {
  step {
    sh 'deploy.sh'
    echo 'Deployment complete'
  }
}

💡 Hint

Steps must be inside the 'steps' block using curly braces.

In Jenkins declarative pipeline, multiple steps must be inside a 'steps' block using curly braces. Option A follows this syntax correctly.

❓ Troubleshoot

advanced

Why does this Jenkins stage fail to run all steps?

Given this Jenkins stage, only the first step runs and the others are skipped. What is the cause?

Jenkins

stage('Test') {
  steps {
    echo 'Running tests'
    return
    echo 'Tests complete'
  }
}

A Jenkins requires each step to be inside its own 'steps' block.

B The stage is missing a 'script' block to run multiple steps.

C The 'echo' command is invalid and causes the stage to stop.

D The 'return' statement exits the steps block early, so later steps are skipped.

💡 Hint

Think about what 'return' does inside a block of code.

The 'return' statement immediately exits the current block or function, so any steps after it are not executed.

🔀 Workflow

advanced

Order of step execution in parallel and sequential stages

In this Jenkins pipeline snippet, which step runs last?

Jenkins

stage('Build') {
  steps {
    echo 'Compile'
  }
}
stage('Test and Package') {
  parallel {
    stage('Test') {
      steps {
        echo 'Run tests'
      }
    }
    stage('Package') {
      steps {
        echo 'Create package'
      }
    }
  }
}
stage('Deploy') {
  steps {
    echo 'Deploy application'
  }
}

A 'Deploy application'

B 'Create package'

C 'Run tests'

D 'Compile'

💡 Hint

Parallel stages run at the same time, but the next stage waits for them to finish.

The 'Deploy' stage runs after 'Build' and the parallel 'Test' and 'Package' stages complete. So 'Deploy application' is printed last.

✅ Best Practice

expert

Best practice for grouping multiple shell commands in a Jenkins step

Which option shows the best way to run multiple shell commands as a single step inside a Jenkins stage?

A

steps {
  sh 'command1 && command2 && command3'
}

B

steps {
  sh 'command1; command2; command3'
}

C

steps {
  sh '''
    command1
    command2
    command3
  '''
}

D

steps {
  sh 'command1'
  sh 'command2'
  sh 'command3'
}

💡 Hint

Think about readability and how Jenkins executes shell commands.

Using a multiline string (triple quotes) inside a single sh step groups commands clearly and runs them in one shell session, improving readability and performance.