Declarative pipeline syntax in Jenkins - Step-by-Step Execution

Process Flow - Declarative pipeline syntax

Start pipeline

↓

Define pipeline block

↓

Specify agent

↓

Define stages

↓

Stage 1: Steps

↓

Stage 2: Steps

↓

Post actions (optional)

↓

Pipeline ends

The declarative pipeline starts with a pipeline block, specifies an agent, defines stages with steps, and optionally post actions before ending.

Execution Sample

Jenkins

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

This pipeline runs on any agent and has one stage 'Build' that prints 'Building...'.

Process Table

Step	Action	Evaluation	Result
1	Start pipeline	pipeline block found	Pipeline execution begins
2	Agent specified	agent any	Runs on any available agent
3	Enter stages block	stages found	Prepare to run stages
4	Enter stage 'Build'	stage('Build') found	Ready to run Build stage
5	Execute steps in 'Build'	steps { echo 'Building...' }	Prints 'Building...' to console
6	No more stages	end of stages	Stages complete
7	No post actions	post block missing	Pipeline ends
8	Pipeline ends	end of pipeline block	Pipeline execution finished

💡 Pipeline completes after all stages and steps run successfully.

Status Tracker

Variable	Start	After Step 2	After Step 5	Final
pipeline	undefined	defined	defined	defined
agent	undefined	any	any	any
stages	undefined	defined	defined	defined
stage 'Build'	undefined	undefined	executing	executed

Key Moments - 3 Insights

Why do we need to specify an agent in the pipeline?

The agent tells Jenkins where to run the pipeline. Without it, Jenkins doesn't know which machine or environment to use. See step 2 in the execution table where 'agent any' means it can run anywhere.

What happens if we forget to put steps inside a stage?

Stages need steps to do work. Without steps, the stage runs but does nothing. In the execution table, step 5 shows the steps block running the echo command. Without it, no action happens.

Can the pipeline run without stages?

No, stages organize the pipeline work. The pipeline block requires stages to define tasks. Step 3 shows entering stages block; without it, the pipeline has no tasks to run.

Visual Quiz - 3 Questions

Look at the execution table, what is the agent value after step 2?

A none

B any

C undefined

D agent not set

💡 Hint

Check the 'agent' row in variable_tracker after Step 2.

At which step does the pipeline print 'Building...'?

A Step 4

B Step 6

C Step 5

D Step 3

💡 Hint

Look at the 'Execute steps in Build' action in the execution_table.

If we add a post block, at which step would it execute?

A After Step 6

B Before Step 4

C After Step 7

D At Step 2

💡 Hint

Post actions run after all stages complete, see step 6 and 7 in execution_table.

Concept Snapshot

Declarative pipeline syntax:
pipeline {
  agent any
  stages {
    stage('Name') {
      steps { ... }
    }
  }
  post { ... }
}
- agent defines where to run
- stages contain ordered tasks
- steps are commands inside stages
- post runs after stages finish

Full Transcript

The declarative pipeline in Jenkins starts with a pipeline block that defines the whole process. Inside, an agent is specified to tell Jenkins where to run the pipeline. Then stages are defined, each with a name and steps that perform actions. For example, a 'Build' stage can have steps that print messages or run commands. After all stages run, optional post actions can execute for cleanup or notifications. The pipeline ends after all these steps complete. This flow ensures Jenkins knows what to do, where, and in what order.