Custom notification logic in Jenkins - Step-by-Step Execution

Process Flow - Custom notification logic

Build Starts

↓

Run Build Steps

↓

Check Build Result

↓

Send Success

↓

End Notification

The build runs, then checks the result. Based on success, failure, or unstable, it sends a custom notification accordingly.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { echo 'Building...' }
    }
  }
  post {
    success { echo 'Notify: Build succeeded' }
    failure { echo 'Notify: Build failed' }
    unstable { echo 'Notify: Build unstable' }
  }
}

A Jenkins pipeline that runs a build and sends different notifications based on the build result.

Process Table

Step	Build Stage	Build Result	Notification Logic	Notification Sent
1	Start Build	N/A	No notification yet	None
2	Run Build Steps	N/A	No notification yet	None
3	Check Result	Success	Trigger success notification	Notify: Build succeeded
4	End	Success	No further notifications	None
5	Restart Build	Failure	Trigger failure notification	Notify: Build failed
6	End	Failure	No further notifications	None
7	Restart Build	Unstable	Trigger unstable notification	Notify: Build unstable
8	End	Unstable	No further notifications	None

💡 Build completes and notification sent based on final build result.

Status Tracker

Variable	Start	After Step 3	After Step 5	After Step 7	Final
buildResult	N/A	Success	Failure	Unstable	Unstable
notificationSent	None	Notify: Build succeeded	Notify: Build failed	Notify: Build unstable	Notify: Build unstable

Key Moments - 3 Insights

Why does the notification only send after the build finishes?

Because the notification logic runs in the 'post' section after all build steps complete, as shown in execution_table rows 3, 5, and 7.

What happens if the build is unstable? Does it send success or failure notification?

It sends the unstable notification only, as seen in execution_table row 7, not success or failure.

Can multiple notifications be sent for one build?

No, only one notification is sent based on the final build result, confirmed by the single notificationSent value per build in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution table, what notification is sent at step 3?

A Notify: Build succeeded

B Notify: Build failed

C Notify: Build unstable

D None

💡 Hint

Check the 'Notification Sent' column at step 3 in the execution_table.

At which step does the build result become 'Failure'?

A Step 7

B Step 3

C Step 5

D Step 8

💡 Hint

Look at the 'Build Result' column in execution_table rows.

If the build result was always 'Success', how many notifications would be sent?

A Multiple notifications per build

B One notification per build

C No notifications

D Notifications only on failure

💡 Hint

Refer to variable_tracker showing notificationSent for 'Success' builds.

Concept Snapshot

Jenkins pipeline uses 'post' section for notifications.
Notifications depend on build result: success, failure, unstable.
Only one notification sent after build finishes.
Use 'success', 'failure', 'unstable' blocks in 'post' to customize.
This ensures clear, condition-based alerts.

Full Transcript

This visual execution shows how Jenkins custom notification logic works. The pipeline runs build steps, then checks the build result. Depending on whether the build succeeded, failed, or was unstable, it sends a matching notification. The notifications happen only after the build finishes, in the 'post' section. The execution table traces each step, showing when notifications trigger. The variable tracker records the build result and notification sent at each key step. Key moments clarify why notifications wait until the end and why only one notification is sent per build. The quiz tests understanding of notification timing and conditions. This helps beginners see exactly how Jenkins decides which notification to send.