Stage block structure in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline stage?

Consider this Jenkins pipeline snippet:

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

What will Jenkins print during the 'Build' stage execution?

Jenkins

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

A

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

B Build

C Building project

D Error: Missing agent declaration

💡 Hint

Look at the echo command inside the steps block.

The echo step prints the string 'Building project' during the 'Build' stage.

❓ Configuration

intermediate

Identify the correct stage block structure for parallel execution

Which Jenkins pipeline snippet correctly defines two parallel stages named 'Test1' and 'Test2' inside a 'Test' stage?

A

stage('Test') {
  parallel {
    stage('Test1') {
      steps { echo 'Running Test1' }
    }
    stage('Test2') {
      steps { echo 'Running Test2' }
    }
  }
}

B

stage('Test') {
  stages {
    parallel {
      stage('Test1') {
        steps { echo 'Running Test1' }
      }
      stage('Test2') {
        steps { echo 'Running Test2' }
      }
    }
  }
}

C

stage('Test') {
  steps {
    parallel {
      stage('Test1') {
        steps { echo 'Running Test1' }
      }
      stage('Test2') {
        steps { echo 'Running Test2' }
      }
    }
  }
}

D

stage('Test') {
  parallel {
    steps {
      stage('Test1') {
        echo 'Running Test1'
      }
      stage('Test2') {
        echo 'Running Test2'
      }
    }
  }
}

💡 Hint

Parallel stages are defined inside a parallel block directly under a stage.

Option A correctly places parallel inside the stage block, with nested stage blocks for each parallel branch.

❓ Troubleshoot

advanced

Why does this Jenkins pipeline fail to run stages sequentially?

Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building'
      }
    }
    parallel {
      stage('Test1') {
        steps {
          echo 'Testing 1'
        }
      }
      stage('Test2') {
        steps {
          echo 'Testing 2'
        }
      }
    }
  }
}

Why does Jenkins report a syntax error?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building'
      }
    }
    parallel {
      stage('Test1') {
        steps {
          echo 'Testing 1'
        }
      }
      stage('Test2') {
        steps {
          echo 'Testing 2'
        }
      }
    }
  }
}

A Because 'agent' is missing inside 'parallel'

B Because 'steps' block is missing inside 'parallel'

C Because 'stage' blocks cannot be nested inside 'stages'

D Because 'parallel' cannot be a direct child of 'stages'; it must be inside a 'stage' block

💡 Hint

Check the Jenkins pipeline syntax rules for where parallel can be placed.

The parallel block must be inside a stage block, not directly inside stages. This causes the syntax error.

🔀 Workflow

advanced

What is the order of execution for these stages in a Jenkins pipeline?

Consider this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { echo 'Build' }
    }
    stage('Test') {
      parallel {
        stage('Unit') {
          steps { echo 'Unit Test' }
        }
        stage('Integration') {
          steps { echo 'Integration Test' }
        }
      }
    }
    stage('Deploy') {
      steps { echo 'Deploy' }
    }
  }
}

What is the correct order of printed messages in the Jenkins console?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { echo 'Build' }
    }
    stage('Test') {
      parallel {
        stage('Unit') {
          steps { echo 'Unit Test' }
        }
        stage('Integration') {
          steps { echo 'Integration Test' }
        }
      }
    }
    stage('Deploy') {
      steps { echo 'Deploy' }
    }
  }
}

A Build, Unit Test and Integration Test (in any order), Deploy

B Unit Test, Integration Test, Build, Deploy

C Build, Deploy, Unit Test, Integration Test

D Build, Unit Test, Deploy, Integration Test

💡 Hint

Remember that parallel stages run simultaneously after the previous stage completes.

The 'Build' stage runs first, then the 'Test' stage runs its parallel branches 'Unit' and 'Integration' simultaneously, then 'Deploy' runs last.

✅ Best Practice

expert

Which stage block structure ensures proper error handling and cleanup?

In Jenkins declarative pipelines, which stage block structure correctly uses post blocks to handle success and cleanup after a stage?

A

stage('Deploy') {
  post {
    success {
      echo 'Deployment succeeded'
    }
    always {
      echo 'Cleanup'
    }
  }
  steps {
    echo 'Deploying'
  }
}

B

stage('Deploy') {
  steps {
    echo 'Deploying'
  }
  post {
    success {
      echo 'Deployment succeeded'
    }
    always {
      echo 'Cleanup'
    }
  }
}

C

stage('Deploy') {
  steps {
    echo 'Deploying'
  }
  post {
    always {
      echo 'Cleanup'
    }
    success {
      echo 'Deployment succeeded'
    }
  }
}

D

stage('Deploy') {
  steps {
    echo 'Deploying'
  }
  post {
    failure {
      echo 'Deployment failed'
    }
  }
}

💡 Hint

The order of post conditions matters for readability and correctness.

Option B correctly places steps first, then post with success and always blocks in proper order.