Why scripted pipelines offer flexibility in Jenkins - Visual Breakdown

Process Flow - Why scripted pipelines offer flexibility

Start Pipeline

↓

Execute Scripted Pipeline

↓

Use Groovy Code

↓

Add Conditions, Loops, Variables

↓

Control Flow Dynamically

↓

Flexible Build Steps

↓

Pipeline Ends

Scripted pipelines run Groovy code step-by-step, allowing dynamic decisions and flexible build steps.

Execution Sample

Jenkins

node {
  if (env.BRANCH_NAME == 'main') {
    echo 'Deploying to production'
  } else {
    echo 'Deploying to staging'
  }
}

This scripted pipeline checks the branch name and prints a message accordingly.

Process Table

Step	Condition Checked	Condition Result	Action Taken	Output
1	env.BRANCH_NAME == 'main'	True	echo 'Deploying to production'	Deploying to production
2	End of script	N/A	Pipeline ends	N/A

💡 Script ends after executing the matching branch condition.

Status Tracker

Variable	Start	After Step 1	Final
env.BRANCH_NAME	main	main	main

Key Moments - 2 Insights

Why can we use if-else conditions in scripted pipelines?

Because scripted pipelines run Groovy code, they allow normal programming constructs like if-else, as shown in step 1 of the execution table.

What happens if the branch name is not 'main'?

The else block runs, printing 'Deploying to staging'. This flexibility comes from using code logic, not fixed steps.

Visual Quiz - 3 Questions

Look at the execution table, what is printed when env.BRANCH_NAME is 'main'?

A Deploying to production

B Deploying to staging

C No output

D Error message

💡 Hint

Check Step 1 output in the execution table.

At which step does the pipeline finish execution?

A Step 1

B Step 3

C Step 2

D It never ends

💡 Hint

Look at the exit note and Step 2 in the execution table.

If we add a loop inside the scripted pipeline, what changes in the execution?

A The output stays the same

B More steps appear in the execution table showing each loop iteration

C The pipeline stops immediately

D The pipeline ignores the loop

💡 Hint

Scripted pipelines allow loops, so execution steps increase accordingly.

Concept Snapshot

Scripted pipelines use Groovy code for builds.
They allow conditions, loops, and variables.
This makes pipelines flexible and dynamic.
You control flow with normal programming logic.
Great for complex build scenarios.

Full Transcript

Scripted pipelines in Jenkins run Groovy code step-by-step. This lets you use programming features like if-else conditions and loops. For example, you can check the branch name and decide what to do next. This flexibility means you can create dynamic build flows that change based on variables or environment. The execution table shows how the pipeline checks the branch and prints a message accordingly. Variables like env.BRANCH_NAME keep their values during execution. Beginners often wonder why scripted pipelines allow if-else; it's because they run real code. Also, if the branch is not 'main', the else block runs, showing flexibility. Adding loops would add more steps to the execution, showing each iteration. This makes scripted pipelines powerful for complex tasks.