Build timeouts in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Pipeline: Timeout Behavior

What will be the output if the following Jenkins pipeline script runs and the 'sleep' step exceeds the timeout duration?

Jenkins

pipeline {
  agent any
  stages {
    stage('Test Timeout') {
      steps {
        timeout(time: 1, unit: 'MINUTES') {
          sleep time: 90, unit: 'SECONDS'
          echo 'Completed sleep'
        }
      }
    }
  }
}

A Build retries the sleep step automatically

B Build completes successfully and prints 'Completed sleep'

C Build is aborted silently without error message

D Build fails with an error: Timeout has been exceeded

💡 Hint

Consider what happens when a step runs longer than the timeout block allows.

The 'timeout' step aborts the build if the enclosed steps exceed the specified time. Here, sleeping for 90 seconds exceeds the 1-minute timeout, causing the build to fail with a timeout error.

❓ Configuration

intermediate

Configuring Build Timeout in Jenkins Freestyle Job

Which configuration snippet correctly sets a build timeout of 10 minutes in a Jenkins freestyle job using the 'Build Timeout' plugin?

A

<hudson.plugins.build_timeout.BuildTimeoutWrapper>
  <timeoutMinutes>10</timeoutMinutes>
  <failBuild>false</failBuild>
</hudson.plugins.build_timeout.BuildTimeoutWrapper>

B

<hudson.plugins.build_timeout.BuildTimeoutWrapper>
  <timeoutMinutes>10</timeoutMinutes>
  <failBuild>true</failBuild>
</hudson.plugins.build_timeout.BuildTimeoutWrapper>

C

<hudson.plugins.build_timeout.BuildTimeoutWrapper>
  <timeoutSeconds>600</timeoutSeconds>
  <failBuild>true</failBuild>
</hudson.plugins.build_timeout.BuildTimeoutWrapper>

D

<hudson.plugins.build_timeout.BuildTimeoutWrapper>
  <timeoutMinutes>600</timeoutMinutes>
  <failBuild>false</failBuild>
</hudson.plugins.build_timeout.BuildTimeoutWrapper>

💡 Hint

Timeout is set in minutes, and failing the build on timeout is common.

The 'timeoutMinutes' field expects the timeout duration in minutes. Setting 'failBuild' to true causes the build to fail if the timeout is reached. Option B correctly sets a 10-minute timeout and fails the build on timeout.

❓ Troubleshoot

advanced

Diagnosing Timeout Not Triggering in Jenkins Pipeline

A Jenkins pipeline uses the 'timeout' step set to 5 minutes, but the build runs for 10 minutes without aborting. What is the most likely cause?

Jenkins

pipeline {
  agent any
  stages {
    stage('Long Task') {
      steps {
        timeout(time: 5, unit: 'MINUTES') {
          sh 'sleep 600'
        }
      }
    }
  }
}

A The 'sleep' command inside 'sh' is not interruptible by Jenkins timeout.

B The 'timeout' step does not work with shell commands like 'sh'.

C The timeout unit is incorrectly set and defaults to seconds.

D The pipeline agent does not support timeouts.

💡 Hint

Think about how Jenkins interrupts running shell commands.

The 'timeout' step can interrupt pipeline steps, but shell commands like 'sleep' may not respond to the interrupt signal properly, causing the timeout to not abort the build as expected.

🔀 Workflow

advanced

Implementing Timeout with Retry in Jenkins Pipeline

Which Jenkins pipeline snippet correctly retries a build stage up to 3 times if it times out after 2 minutes each attempt?

A

stage('Retry Timeout') {
  steps {
    retry(3) {
      timeout(time: 2, unit: 'MINUTES') {
        sh 'run_tests.sh'
      }
    }
  }
}

B

stage('Retry Timeout') {
  steps {
    timeout(time: 2, unit: 'MINUTES') {
      retry(3) {
        sh 'run_tests.sh'
      }
    }
  }
}

C

stage('Retry Timeout') {
  steps {
    retry(3) {
      sh 'timeout 2m run_tests.sh'
    }
  }
}

D

stage('Retry Timeout') {
  steps {
    sh 'run_tests.sh'
    timeout(time: 2, unit: 'MINUTES') {
      retry(3) {
        echo 'Retrying'
      }
    }
  }
}

💡 Hint

Timeout should wrap the command inside the retry block to retry on timeout.

Wrapping the 'timeout' step inside the 'retry' block ensures that if the timeout occurs, the stage is retried up to 3 times. Option A correctly places 'timeout' inside 'retry'.

✅ Best Practice

expert

Best Practice for Setting Build Timeout in Jenkins Declarative Pipeline

Which approach is the best practice to set a global build timeout of 15 minutes for all stages in a Jenkins declarative pipeline?

A Set the timeout in the Jenkins global configuration only.

B Wrap each stage with a 'timeout' block set to 15 minutes.

C

Use the 'options' directive with 'timeout' at the pipeline level:
options { timeout(time: 15, unit: 'MINUTES') }

D Use a 'timeout' step inside the 'post' section to abort after 15 minutes.

💡 Hint

Consider how to apply timeout globally in declarative pipelines.

Using the 'options' directive with 'timeout' at the pipeline level applies the timeout globally to the entire build, which is cleaner and less error-prone than wrapping each stage individually.