Conditional deployment logic in Jenkins - Step-by-Step Execution

Process Flow - Conditional deployment logic

Start Pipeline

↓

Check Condition

↓

Deploy

↓

End Pipeline

The pipeline starts, checks a condition, then either deploys if true or skips deployment if false, then ends.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Deploy') {
      when { branch 'main' }
      steps { echo 'Deploying...' }
    }
  }
}

This Jenkins pipeline deploys only if the branch is 'main'.

Process Table

Step	Condition Checked	Condition Result	Action Taken	Output
1	Is branch 'main'?	True	Execute deploy stage	Deploying...
2	Pipeline ends	-	Finish	Pipeline completed successfully

💡 Pipeline ends after deployment stage completes because condition was true.

Status Tracker

Variable	Start	After Step 1	After Step 2
branch	main	main	main
deploy_stage_executed	false	true	true

Key Moments - 2 Insights

Why does the deploy stage run only when the branch is 'main'?

Because the 'when' condition checks the branch name. In the execution table row 1, the condition is true only if branch equals 'main', triggering deployment.

What happens if the branch is not 'main'?

The deploy stage is skipped. The condition in row 1 would be false, so no deploy action occurs and pipeline ends without deployment.

Visual Quiz - 3 Questions

Look at the execution table, what is the output at step 1?

A Skipping deployment

B Pipeline failed

C Deploying...

D No output

💡 Hint

Check the 'Output' column in execution_table row 1.

At which step does the pipeline finish?

A Step 1

B Step 2

C Before Step 1

D After Step 3

💡 Hint

Look at the 'Action Taken' column for pipeline completion.

If the branch was 'feature', what would happen to 'deploy_stage_executed' variable?

A It would remain false

B It would be undefined

C It would be true

D It would cause an error

💡 Hint

Refer to variable_tracker and key_moments about condition false case.

Concept Snapshot

Jenkins conditional deployment uses 'when' to check conditions.
If condition true, deploy stage runs.
If false, stage is skipped.
Common use: deploy only on 'main' branch.
Helps avoid unwanted deployments.

Full Transcript

This Jenkins pipeline example shows conditional deployment logic. The pipeline starts and checks if the current branch is 'main'. If yes, it runs the deploy stage and prints 'Deploying...'. If not, it skips deployment. The execution table traces these steps clearly. Variables track the branch name and whether deployment ran. Key moments clarify why deployment depends on the branch and what happens if the condition is false. The visual quiz tests understanding of outputs and variable states. The snapshot summarizes how Jenkins uses 'when' conditions to control deployment stages.