Build timeouts in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a build timeout of 10 minutes in a Jenkins pipeline.

Jenkins

timeout(time: [1], unit: 'MINUTES') {
  // build steps
}

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

A20

B15

C5

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a number for the time value.

Setting the time too low or too high without reason.

The timeout step requires the time value in minutes. Setting it to 10 means the build will stop if it runs longer than 10 minutes.

2fill in blank

medium

Complete the code to set a build timeout using the 'timeout' step with a unit of 'SECONDS'.

Jenkins

timeout(time: [1], unit: 'SECONDS') {
  // build steps
}

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

A60

B120

C30

D300

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing seconds with minutes.

Choosing a time too short for the build.

Setting the timeout to 60 seconds means the build will be stopped if it runs longer than 1 minute.

3fill in blank

hard

Fix the error in the timeout step by completing the missing unit value.

Jenkins

timeout(time: 5, unit: '[1]') {
  // build steps
}

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

AMINUTES

BHOURS

CSECONDS

DDAYS

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase units like 'minutes' instead of uppercase.

Choosing a unit that does not match the time value.

The unit must be one of the supported strings. 'MINUTES' is the correct unit for a 5-minute timeout.

4fill in blank

hard

Fill both blanks to set a timeout of 2 hours using the Jenkins pipeline syntax.

Jenkins

timeout(time: [1], unit: '[2]') {
  // build steps
}

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

A2

B120

CHOURS

DMINUTES

Attempts:

3 left

💡 Hint

Common Mistakes

Using 120 with 'HOURS' which would mean 120 hours.

Using 'MINUTES' with 2 which means 2 minutes, not 2 hours.

Setting time to 2 and unit to 'HOURS' means the build will timeout after 2 hours.

5fill in blank

hard

Fill all three blanks to create a timeout block that stops the build after 90 minutes.

Jenkins

timeout(time: [1], unit: '[2]') {
  echo '[3]'
}

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

A90

BMINUTES

CBuild timed out after 90 minutes

DSECONDS

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'SECONDS' instead of 'MINUTES' for the unit.

Setting time to 90 but using 'SECONDS' which means 90 seconds.

The timeout is set to 90 minutes, and the echo message informs that the build timed out after 90 minutes.

Practice

1. What is the main purpose of using timeout in a Jenkins build step?

easy

A. To log the build step output for debugging

B. To increase the build step execution time automatically

C. To restart the build step if it fails

D. To limit how long a build step runs to avoid stuck builds

Solution

1. Step 1: Understand the role of timeout in Jenkins

   The timeout directive is used to set a maximum time limit for a build step to run.

2. Step 2: Identify the benefit of limiting build step time

   Limiting time prevents builds from hanging indefinitely and wasting resources.

3. Final Answer:

   To limit how long a build step runs to avoid stuck builds -> Option D

4. Quick Check:

   Timeout limits build step time = A [OK]

Hint: Timeout stops long builds to save resources [OK]

Common Mistakes:

• Thinking timeout extends build time
• Confusing timeout with retry logic
• Assuming timeout logs output automatically

2. Which of the following is the correct syntax to set a timeout of 10 minutes in a Jenkins pipeline?

easy

A. timeout(time: 10, unit: 'MINUTES') { /* steps */ }

B. timeout(10 minutes) { /* steps */ }

C. timeout { time: 10, unit: 'MINUTES' }

D. timeout(time=10, unit='minutes') { /* steps */ }

Solution

1. Step 1: Recall Jenkins timeout syntax

   The correct syntax uses named parameters: timeout(time: 10, unit: 'MINUTES').

2. Step 2: Check each option for syntax correctness

   timeout(time: 10, unit: 'MINUTES') { /* steps */ } matches the correct syntax. The other options have syntax errors or wrong parameter formats.

3. Final Answer:

   timeout(time: 10, unit: 'MINUTES') { /* steps */ } -> Option A

4. Quick Check:

   Named params with colon and quotes = B [OK]

Hint: Use named params with colon and quotes for timeout [OK]

Common Mistakes:

• Using parentheses without named params
• Wrong parameter separators like = instead of :
• Missing quotes around unit string

3. Given this Jenkins pipeline snippet:

timeout(time: 1, unit: 'MINUTES') {
  sh 'sleep 90'
}

What will happen when this pipeline runs?

medium

A. The build step will complete successfully after 90 seconds

B. The build step will timeout and be aborted after 1 minute

C. The build step will ignore the timeout and run for 90 seconds

D. The build will fail immediately due to syntax error

Solution

1. Step 1: Analyze the timeout and sleep duration

   The timeout is set to 1 minute, but the shell command sleeps for 90 seconds (1.5 minutes).

2. Step 2: Understand timeout behavior

   Since the sleep exceeds the timeout, Jenkins will abort the build step after 1 minute.

3. Final Answer:

   The build step will timeout and be aborted after 1 minute -> Option B

4. Quick Check:

   Sleep > timeout causes abort = D [OK]

Hint: If step runs longer than timeout, Jenkins aborts it [OK]

Common Mistakes:

• Assuming step completes despite timeout
• Confusing timeout unit or value
• Thinking syntax error occurs here

4. You added a timeout to your Jenkins pipeline but it does not abort the build when expected. Which is the most likely cause?

medium

A. The timeout unit is misspelled or invalid

B. The timeout block is placed outside the pipeline script

C. The timeout value is set longer than the step duration

D. The Jenkins server is offline

Solution

1. Step 1: Check timeout configuration

   The most likely cause is that the timeout value is set longer than the actual step duration, so no timeout occurs even if expected.

2. Step 2: Evaluate other options

   Timeout block outside pipeline or invalid unit would cause syntax errors preventing execution. Server offline prevents builds from running.

3. Final Answer:

   The timeout value is set longer than the step duration -> Option C

4. Quick Check:

   Timeout value longer than step = A [OK]

Hint: Verify timeout value vs step duration if no abort [OK]

Common Mistakes:

• Placing timeout outside pipeline block
• Setting timeout longer than step time expecting abort
• Ignoring Jenkins server status

5. You want to ensure a Jenkins build step is aborted if it runs longer than 5 minutes, but you also want to retry the step up to 2 times if it fails due to timeout. Which pipeline snippet correctly implements this?

hard

A. retry(2) {
timeout(time: 5, unit: 'MINUTES') {
sh 'run-step.sh'
}
}

B. timeout(time: 5, unit: 'MINUTES') {
retry(2) {
sh 'run-step.sh'
}
}

C. timeout(time: 5, unit: 'MINUTES', retry: 2) {
sh 'run-step.sh'
}

D. retry(2, timeout(time: 5, unit: 'MINUTES')) {
sh 'run-step.sh'
}

Solution

1. Step 1: Understand retry and timeout nesting

   To retry a step if it times out, the timeout block must be inside the retry block so the whole timeout step is retried.

2. Step 2: Evaluate each option's structure

   retry(2) { timeout(time: 5, unit: 'MINUTES') { sh 'run-step.sh' } } correctly nests timeout inside retry. timeout(time: 5, unit: 'MINUTES') { retry(2) { sh 'run-step.sh' } } retries the inner command but timeout applies only once. The remaining options use invalid syntax.

3. Final Answer:

   retry(2) { timeout(time: 5, unit: 'MINUTES') { sh 'run-step.sh' } } -> Option A

4. Quick Check:

   retry outside timeout retries whole timeout block = A [OK]

Hint: Put timeout inside retry to retry timed-out steps [OK]

Common Mistakes:

• Placing retry inside timeout causing no retry on timeout
• Using invalid parameters in timeout
• Misunderstanding retry scope