Why knowing alternatives matters in Jenkins - See It in Action

Why Knowing Alternatives Matters in Jenkins

📖 Scenario: You are a DevOps engineer working with Jenkins to automate software builds. Sometimes, Jenkins plugins or features may not fit your needs perfectly. Knowing alternative ways to achieve the same goal helps you stay flexible and solve problems faster.

🎯 Goal: Build a simple Jenkins pipeline script that demonstrates using a basic build step, then add a configuration variable to choose an alternative build command, and finally use conditional logic to run the chosen command. This shows why knowing alternatives matters in automation.

📋 What You'll Learn

Create a Jenkins pipeline script with a variable for the build command

Add a configuration variable to select between two build commands

Use conditional logic to run the selected build command

Print the command being run to the console

💡 Why This Matters

🌍 Real World

In real projects, Jenkins pipelines automate builds and tests. Sometimes plugins or commands change, so knowing alternative commands helps keep pipelines working smoothly.

💼 Career

DevOps engineers must write flexible Jenkins pipelines. Understanding alternatives and conditional logic is key to maintaining reliable automation.

1

Create a basic Jenkins pipeline with a build command

Write a Jenkins pipeline script with a pipeline block and a stage named 'Build'. Inside the stage, add a steps block that runs the shell command 'echo Building project with default command' using sh.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
    }
}

Need a hint?

Use sh 'echo ...' inside steps to run a shell command.

2

Add a configuration variable to select the build command

Add a def variable named buildCommand at the top of the script and set it to 'echo Building with default command'. This variable will hold the build command to run.

Jenkins

def buildCommand = 'echo Building with default command'

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
    }
}

Need a hint?

Define buildCommand before the pipeline block and use it inside sh.

3

Add an alternative build command and conditional logic

Add a def variable named useAlternative and set it to true. Then, use a script block inside steps to set buildCommand to 'echo Building with alternative command' if useAlternative is true. Otherwise, keep the default command.

Jenkins

def buildCommand = 'echo Building with default command'
def useAlternative = true

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                script {
                    // Your code here
                }
                sh buildCommand
            }
        }
    }
}

Need a hint?

Use if (useAlternative) { buildCommand = ... } inside a script block.

4

Print the build command being run

Add a echo step before running sh buildCommand to print 'Running command: ' followed by the value of buildCommand.

Jenkins

def buildCommand = 'echo Building with default command'
def useAlternative = true

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                script {
                    if (useAlternative) {
                        buildCommand = 'echo Building with alternative command'
                    }
                }
                // Your code here
                sh buildCommand
            }
        }
    }
}

Need a hint?

Use echo "Running command: ${buildCommand}" before sh buildCommand.