When to use scripted over declarative in Jenkins - Step-by-Step Execution

Process Flow - When to use scripted over declarative

Start Pipeline

↓

Choose Pipeline Type

↓

Declarative

The flow shows starting a Jenkins pipeline, choosing between declarative for simple, standard cases, or scripted for complex, custom logic needs.

Execution Sample

Jenkins

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

A simple declarative pipeline that runs a build stage printing a message.

Process Table

Step	Pipeline Type	Reason for Choice	Action Taken	Result
1	Declarative	Simple linear flow	Define stages and steps	Pipeline runs with clear structure
2	Declarative	Standard CI/CD tasks	Use built-in syntax	Easy to read and maintain
3	Scripted	Need complex logic	Write Groovy code with loops/conditions	Flexible control over flow
4	Scripted	Custom error handling	Use try-catch blocks	Handle errors precisely
5	Declarative	Limited scripting needed	Use scripted blocks inside declarative	Balance simplicity and flexibility
6	End	-	-	Pipeline completes or fails based on logic

💡 Pipeline finishes after all stages or error handling completes

Status Tracker

Variable	Start	After Step 1	After Step 3	Final
pipelineType	undefined	declarative	scripted	scripted
stage	none	Build	Custom Logic	Custom Logic
errorHandled	false	false	true	true

Key Moments - 2 Insights

Why choose scripted pipeline for complex logic?

Scripted pipelines allow full Groovy code use, enabling loops, conditions, and error handling not easily done in declarative (see execution_table rows 3 and 4).

Can declarative pipelines include scripted parts?

Yes, declarative pipelines support scripted blocks for complex steps, balancing simplicity and flexibility (see execution_table row 5).

Visual Quiz - 3 Questions

Look at the execution table, which step shows using try-catch for error handling?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Reason for Choice' column for 'Custom error handling'

At which step does the pipeline type change to scripted?

A Step 1

B Step 3

C Step 5

D Step 6

💡 Hint

Look at the 'Pipeline Type' column for the first mention of 'scripted'

If you want easy to maintain pipelines with standard tasks, which pipeline type is best?

A Declarative

B Neither

C Scripted

D Both equally

💡 Hint

Refer to execution_table rows 1 and 2 about simple linear flow and standard tasks

Concept Snapshot

Jenkins pipelines come in two types:
- Declarative: simple, readable, good for standard CI/CD
- Scripted: flexible, Groovy-based, for complex logic
Use declarative for most cases; use scripted when you need loops, conditions, or custom error handling.
Declarative can include scripted blocks for extra flexibility.

Full Transcript

This visual execution shows when to use scripted versus declarative Jenkins pipelines. Start by choosing pipeline type. Declarative pipelines are best for simple, standard tasks with clear stages and steps. Scripted pipelines allow full Groovy coding for complex logic like loops and error handling. You can mix scripted blocks inside declarative pipelines for flexibility. The execution table traces steps choosing pipeline type, reasons, actions, and results. Variable tracking shows pipelineType changing from declarative to scripted when complex logic is needed. Key moments clarify why scripted is chosen for custom logic and that declarative can include scripted parts. The quiz tests understanding of these choices referencing the execution table. The snapshot summarizes the main points for quick recall.