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.

Practice

1. What is the main purpose of using Slack notifications in Jenkins pipelines?

easy

A. To schedule Jenkins jobs automatically

B. To store Jenkins job logs permanently

C. To create new Jenkins jobs from Slack

D. To instantly update the team about Jenkins job results

Solution

1. Step 1: Understand the role of Slack notifications

   Slack notifications are used to send messages to a team channel or user to keep them informed.

2. Step 2: Connect to Jenkins job results

   In Jenkins, Slack notifications are commonly used to inform the team about the success or failure of jobs immediately.

3. Final Answer:

   To instantly update the team about Jenkins job results -> Option D

4. Quick Check:

   Slack notifications = team updates [OK]

Hint: Slack notifications = team updates on job status [OK]

Common Mistakes:

• Confusing notifications with job scheduling
• Thinking Slack stores logs
• Assuming Slack creates Jenkins jobs

2. Which Jenkins pipeline syntax correctly sends a Slack message after a job completes?

easy

A. steps { slackSend channel: '#team', message: 'Job done!' }

B. post { always { slackSend channel: '#team', message: 'Job done!' } }

C. stage('Notify') { slackSend channel: '#team', message: 'Job done!' }

D. pipeline { slackSend channel: '#team', message: 'Job done!' }

Solution

1. Step 1: Identify correct placement of slackSend

   The slackSend step must be inside the post section to run after job completion.

2. Step 2: Check syntax correctness

   post { always { slackSend channel: '#team', message: 'Job done!' } } uses post { always { slackSend ... } } which is the correct syntax to send notifications after any build result.

3. Final Answer:

   post { always { slackSend channel: '#team', message: 'Job done!' } } -> Option B

4. Quick Check:

   slackSend inside post always = correct [OK]

Hint: Use slackSend inside post block for notifications [OK]

Common Mistakes:

• Placing slackSend directly in steps or pipeline block
• Missing the post block
• Incorrect block nesting

3. Given this Jenkins pipeline snippet, what will happen when the job finishes successfully?

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

medium

A. A Slack message 'Build succeeded!' is sent to #dev channel

B. No Slack message is sent because slackSend is outside stages

C. Slack message is sent only if the build fails

D. The pipeline will fail due to syntax error

Solution

1. Step 1: Analyze the post success block

   The post { success { ... } } block runs only if the job finishes successfully.

2. Step 2: Understand slackSend behavior

   The slackSend step inside success sends the message to the specified Slack channel.

3. Final Answer:

   A Slack message 'Build succeeded!' is sent to #dev channel -> Option A

4. Quick Check:

   post success runs slackSend = message sent [OK]

Hint: post success block sends Slack message on success [OK]

Common Mistakes:

• Thinking slackSend must be inside stages
• Confusing success with failure block
• Assuming syntax error without checking carefully

4. You added this snippet to your Jenkinsfile but no Slack notifications are sent:

post {
  always {
    slackSend channel: '#alerts', message: 'Job finished'
  }
}

What is the most likely reason for this?

medium

A. The channel name must start with '@' instead of '#'

B. The post block must be inside a stage block

C. Slack plugin is not configured or Slack token is missing

D. The slackSend step requires a username parameter

Solution

1. Step 1: Check Slack plugin and token setup

   Slack notifications require the Slack plugin installed and a valid Slack token configured in Jenkins.

2. Step 2: Verify syntax and usage

   The post block with slackSend is correctly placed; missing or incorrect Slack configuration is the common cause of no messages.

3. Final Answer:

   Slack plugin is not configured or Slack token is missing -> Option C

4. Quick Check:

   Missing Slack config = no notifications [OK]

Hint: Check Slack plugin and token if no messages appear [OK]

Common Mistakes:

• Placing post block inside stage incorrectly
• Assuming username is mandatory
• Using wrong channel prefix

5. You want to send a Slack notification only when a Jenkins job fails, but also include the job name and build number in the message. Which pipeline snippet correctly achieves this?

hard

A. post { failure { slackSend channel: '#alerts', message: "Job ${env.JOB_NAME} #${env.BUILD_NUMBER} failed" } }

B. post { always { slackSend channel: '#alerts', message: 'Job failed' } }

C. post { failure { slackSend channel: '#alerts', message: 'Job failed' } }

D. post { failure { slackSend channel: '#alerts', message: 'Job $JOB_NAME #$BUILD_NUMBER failed' } }

Solution

1. Step 1: Use failure block for failure-only notifications

   The post { failure { ... } } block runs only when the job fails.

2. Step 2: Use correct Groovy string interpolation for environment variables

   In Jenkins pipeline, environment variables are accessed via env.VAR_NAME inside double quotes with ${} syntax.

3. Step 3: Verify message content includes job name and build number

   post { failure { slackSend channel: '#alerts', message: "Job ${env.JOB_NAME} #${env.BUILD_NUMBER} failed" } } correctly uses "Job ${env.JOB_NAME} #${env.BUILD_NUMBER} failed" to include dynamic info.

4. Final Answer:

   post { failure { slackSend channel: '#alerts', message: "Job ${env.JOB_NAME} #${env.BUILD_NUMBER} failed" } } -> Option A

5. Quick Check:

   failure block + env vars with ${} = correct [OK]

Hint: Use failure block and ${env.VAR} for dynamic Slack messages [OK]

Common Mistakes:

• Using single quotes which disable variable interpolation
• Referencing env vars without env prefix
• Sending notifications on all results instead of failure only