Slack notifications in Jenkins - Step-by-Step Execution

Process Flow - Slack notifications

Jenkins Job Starts

↓

Build Executes

↓

Check Build Result

↓

Send Slack

↓

Success Msg

↓

Notification Sent

Jenkins runs a job, checks if it succeeded or failed, then sends a Slack message accordingly.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { echo 'Building...' }
    }
  }
  post {
    success { slackSend channel: '#general', message: 'Build succeeded!' }
    failure { slackSend channel: '#general', message: 'Build failed!' }
  }
}

This Jenkins pipeline sends a Slack message to #general channel after build success or failure.

Process Table

Step	Build Status	Action	Slack Message	Notification Sent
1	N/A	Start build	N/A	No
2	Running	Execute build steps	N/A	No
3	Success	Check post conditions	Build succeeded!	Yes
4	End	Finish pipeline	N/A	No further notifications

💡 Build completed successfully, Slack notification sent with success message.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
buildStatus	N/A	Running	Success	Success
slackMessage	N/A	N/A	Build succeeded!	Build succeeded!
notificationSent	No	No	Yes	Yes

Key Moments - 2 Insights

Why does the Slack message only send after the build finishes?

Slack notifications are triggered in the 'post' section after the build completes, as shown in execution_table step 3.

What happens if the build fails instead of succeeding?

If the build fails, the 'failure' block sends a failure message to Slack instead of the success message, changing slackMessage in step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the buildStatus at step 2?

A Failure

B Success

C Running

D N/A

💡 Hint

Check the 'Build Status' column in execution_table row for step 2.

At which step is the Slack notification sent?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Notification Sent' column in execution_table.

If the build failed, what would slackMessage be at step 3?

A 'Build succeeded!'

B 'Build failed!'

C No message sent

D 'Build running...'

💡 Hint

Refer to key_moments explanation about failure message.

Concept Snapshot

Jenkins Slack Notifications:
- Use 'post' section in pipeline for notifications
- 'success' and 'failure' blocks send messages
- Use slackSend step with channel and message
- Notifications happen after build completes
- Customize messages per build result

Full Transcript

This visual execution shows how Jenkins sends Slack notifications after a build. The pipeline starts, runs build steps, then checks if the build succeeded or failed. Depending on the result, it sends a Slack message to a channel. Variables like buildStatus and slackMessage update step-by-step. Notifications only send after the build finishes, ensuring accurate status updates.