Build timeouts in Jenkins - Step-by-Step Execution

Process Flow - Build timeouts

Start Build

↓

Start Timer

↓

Build Running

↓

Check Timeout?

No→Continue Build

Yes↓

Abort Build

↓

Build Ends

The build starts and a timer runs. If the build runs longer than the timeout, Jenkins aborts it. Otherwise, it continues until done.

Execution Sample

Jenkins

timeout(time: 5, unit: 'MINUTES') {
  sh 'sleep 300'
}

This Jenkins pipeline snippet runs a shell command that sleeps for 300 seconds with a 5-minute timeout.

Process Table

Step	Action	Timer Status	Build Status	Output
1	Start build and timer	0 min elapsed	Running	Build started
2	Run shell command 'sleep 300'	1 min elapsed	Running	Sleeping...
3	Run shell command continues	4 min elapsed	Running	Still sleeping...
4	Timer reaches 5 minutes	5 min elapsed	Timeout triggered	Build aborted due to timeout
5	Build ends	Stopped	Aborted	Build stopped because timeout exceeded

💡 Build aborted because the timeout of 5 minutes was reached while the sleep command was still running.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Timer (minutes elapsed)	0	0	1	4	5	Stopped
Build Status	Not started	Running	Running	Running	Timeout triggered	Aborted

Key Moments - 2 Insights

Why does the build abort exactly at 5 minutes?

Because the timeout is set to 5 minutes, Jenkins monitors the elapsed time and aborts the build as soon as it reaches this limit, as shown in step 4 of the execution table.

What happens if the build finishes before the timeout?

If the build finishes before the timeout, Jenkins stops the timer and completes the build normally. This is implied by the flow where 'Check Timeout?' leads to 'Continue Build' if no timeout occurs.

Visual Quiz - 3 Questions

Look at the execution table, what is the build status at step 3?

A Aborted

B Not started

C Running

D Completed

💡 Hint

Check the 'Build Status' column at step 3 in the execution table.

At which step does the timeout trigger the build abort?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Look for 'Timeout triggered' in the 'Build Status' column in the execution table.

If the timeout was set to 10 minutes instead of 5, what would change in the execution table?

A Build would never abort at 5 minutes

B Timer would reach 10 minutes before aborting

C Build would abort at step 4

D Build would abort immediately

💡 Hint

Refer to the 'Timer Status' and 'Build Status' columns and how timeout triggers abort.

Concept Snapshot

Build timeouts in Jenkins stop builds that run too long.
Use the 'timeout' step with time and unit.
If build exceeds time, Jenkins aborts it.
Prevents stuck or slow builds.
Example: timeout(time:5, unit:'MINUTES') { ... }

Full Transcript

In Jenkins, build timeouts help stop builds that take too long. When a build starts, Jenkins starts a timer. If the build finishes before the timeout, it completes normally. If the build runs longer than the timeout, Jenkins aborts it to save resources. For example, using the 'timeout' step with 5 minutes means if the build runs over 5 minutes, Jenkins stops it. This prevents builds from hanging forever. The execution table shows the timer increasing each step and the build status changing to aborted when the timeout is reached.