Why notifications matter in Jenkins - See It in Action

Why notifications matter

📖 Scenario: You are managing a Jenkins pipeline that builds and tests software. You want to make sure your team knows immediately if the build fails or succeeds. Notifications help keep everyone informed and reduce delays in fixing problems.

🎯 Goal: Build a simple Jenkins pipeline script that sends notifications when the build status changes. You will create the pipeline steps, add a notification configuration, implement the notification logic, and finally display the notification message.

📋 What You'll Learn

Create a Jenkins pipeline with a build stage

Add a variable to hold the notification message

Use a post block to send notifications on build success or failure

Print the notification message at the end

💡 Why This Matters

🌍 Real World

In real projects, notifications keep the team informed about build results quickly, so they can fix issues or proceed with deployments without delay.

💼 Career

Understanding Jenkins notifications is essential for DevOps engineers to maintain smooth CI/CD pipelines and improve team communication.

1

Create a Jenkins pipeline with a build stage

Write a Jenkins pipeline script that defines a pipeline with an agent any and a stage named Build that runs a simple shell command echo "Building project".

Jenkins

// Your code here

Need a hint?

Start with pipeline { agent any stages { stage('Build') { steps { sh 'echo "Building project"' } } } }

2

Add a variable to hold the notification message

Add a def variable called notificationMessage at the top of the pipeline script and set it to an empty string ''.

Jenkins

def notificationMessage = ''

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh 'echo "Building project"'
            }
        }
    }
}

// Your code here

Need a hint?

Define def notificationMessage = '' before the pipeline block.

3

Use a post block to send notifications on build success or failure

Inside the pipeline block, add a post section with success and failure blocks. Set notificationMessage to 'Build succeeded!' on success and 'Build failed!' on failure.

Jenkins

def notificationMessage = ''

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh 'echo "Building project"'
            }
        }
    }
    // Add post block here
}

// Your code here

Need a hint?

Use post { success { script { notificationMessage = 'Build succeeded!' } } failure { script { notificationMessage = 'Build failed!' } } }

4

Print the notification message at the end

Add a post block with an always section that prints the notificationMessage using echo.

Jenkins

def notificationMessage = ''

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh 'echo "Building project"'
            }
        }
    }
    post {
        success {
            script {
                notificationMessage = 'Build succeeded!'
            }
        }
        failure {
            script {
                notificationMessage = 'Build failed!'
            }
        }
        // Add always block here
    }
}

// Your code here

Need a hint?

Use post { always { echo "${notificationMessage}" } } to print the message.