Why When to use scripted over declarative in Jenkins? - Purpose & Use Cases

The Big Idea

What if your pipeline could think and decide exactly what to do next, like a smart assistant?

The Scenario

Imagine you have a complex project with many unique steps and conditions. You try to write your Jenkins pipeline by manually scripting every detail without a clear structure.

The Problem

This manual scripting becomes confusing and hard to maintain. Small changes break the flow, and it's easy to make mistakes that stop your builds.

The Solution

Using scripted pipelines in Jenkins lets you write flexible, step-by-step code that handles complex logic clearly. It gives you full control to customize your build process exactly how you want.

Before vs After

✗ Before

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

✓ After

node {
  stage('Build') {
    echo 'Building...'
  }
  if (env.BRANCH_NAME == 'main') {
    stage('Deploy') {
      echo 'Deploying to production'
    }
  }
}

What It Enables

Scripted pipelines enable you to handle complex workflows and custom logic that declarative pipelines can't easily express.

Real Life Example

A team needs to run different tests and deploy steps depending on many conditions like branch name, environment variables, or external approvals. Scripted pipelines let them write this logic clearly and flexibly.

Key Takeaways

Manual scripting without structure is error-prone and hard to maintain.

Scripted pipelines give full control for complex, custom workflows.

Use scripted when your build needs logic that declarative can't handle easily.