Agent directive in Jenkins - Step-by-Step Execution

Process Flow - Agent directive

Start Pipeline

↓

Check Agent Directive

↓

Agent Specified

↓

Allocate Agent

↓

Execute Steps

↓

Pipeline Ends

The pipeline starts, checks if an agent is specified, allocates it if yes, or runs on master if no, then executes steps and ends.

Execution Sample

Jenkins

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

This Jenkins pipeline uses the agent directive to run on any available agent and executes a build stage.

Process Table

Step	Action	Agent Directive	Agent Allocated	Pipeline Step Executed	Output
1	Start pipeline	agent any	Not allocated yet	No	Pipeline started
2	Check agent directive	agent any	Allocating any available agent	No	Agent allocation in progress
3	Agent allocated	agent any	Agent #5 allocated	No	Agent ready
4	Execute stage 'Build'	agent any	Agent #5 allocated	Yes	Building...
5	Pipeline ends	agent any	Agent #5 released	No	Pipeline completed

💡 Pipeline ends after all stages complete and agent is released

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Agent Directive	agent any	agent any	agent any	agent any	agent any
Agent Allocated	None	Allocating	Agent #5	Agent #5	Released
Pipeline Step Executed	No	No	No	Yes	No

Key Moments - 2 Insights

Why does the pipeline allocate an agent before running steps?

Because the 'agent any' directive tells Jenkins to find any available agent before executing steps, as shown in execution_table row 3.

What happens if no agent directive is specified?

The pipeline runs on the master node by default, skipping agent allocation, which differs from the flow shown here.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the agent actually allocated?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Check the 'Agent Allocated' column in execution_table row 3

According to variable_tracker, what is the state of 'Pipeline Step Executed' after step 3?

A No

B Yes

C Allocating

D Released

💡 Hint

Look at the 'Pipeline Step Executed' row, column 'After Step 3'

If the agent directive was removed, how would the 'Agent Allocated' column change?

A It would show 'Agent #5 allocated' as before

B It would show 'No agent allocated, runs on master'

C It would show 'Allocating any available agent'

D It would show 'Agent released immediately'

💡 Hint

Recall the key moment about default behavior without agent directive

Concept Snapshot

Jenkins 'agent' directive tells where to run pipeline steps.
Syntax: agent any | none | label 'name'
If agent specified, Jenkins allocates it before running steps.
Without agent, runs on master node by default.
Agent is released after pipeline completes.

Full Transcript

This visual execution shows how Jenkins pipeline uses the agent directive. The pipeline starts and checks if an agent is specified. If yes, it allocates an agent before running the steps. Here, 'agent any' means any available agent is allocated. The build stage runs on that agent. After all stages finish, the agent is released and the pipeline ends. If no agent directive is given, the pipeline runs on the master node by default. Variables like 'Agent Allocated' and 'Pipeline Step Executed' track the state changes during execution.