Slack notifications in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of Slack notifications in Jenkins?

Slack notifications in Jenkins are used to send messages about build status or pipeline events directly to Slack channels, helping teams stay informed in real time.

beginner

Which Jenkins plugin is commonly used to send Slack notifications?

The 'Slack Notification Plugin' is commonly used to integrate Jenkins with Slack for sending build and pipeline notifications.

beginner

What information do you need from Slack to configure Jenkins notifications?

You need the Slack workspace's 'Webhook URL' or 'Integration Token' and the target Slack channel name to configure Jenkins Slack notifications.

intermediate

How do you add Slack notifications to a Jenkins pipeline script?

You use the 'slackSend' step in the Jenkins pipeline script with parameters like 'channel', 'message', and optionally 'color' to send notifications.

intermediate

What does the 'color' parameter in Slack notifications control?

The 'color' parameter controls the color of the message attachment in Slack, often used to indicate status like 'good' (green), 'warning' (yellow), or 'danger' (red).

Which Jenkins plugin do you install to enable Slack notifications?

A Docker Plugin

B Git Plugin

C Email Extension Plugin

D Slack Notification Plugin

The Slack Notification Plugin is specifically designed to send notifications from Jenkins to Slack.

What is required to send Slack notifications from Jenkins?

A Slack webhook URL or token and channel name

B Slack username and password

C Slack app installation on Jenkins server

D Slack direct message ID

Jenkins needs the Slack webhook URL or token and the channel name to send notifications.

In a Jenkins pipeline, which command sends a Slack message?

A sendSlackMessage

B slackSend

C notifySlack

D postSlack

The 'slackSend' step is the correct command to send Slack notifications in Jenkins pipelines.

What does setting 'color: "danger"' do in a Slack notification?

A Shows a red message indicating failure or error

B Shows a green message indicating success

C Shows a yellow message indicating warning

D No effect on message color

The 'danger' color sets the message attachment color to red, signaling failure or error.

Where do Slack notifications typically appear when sent from Jenkins?

A In email inbox

B In Jenkins console output only

C In a specified Slack channel

D In Jenkins system logs

Slack notifications appear in the Slack channel configured in Jenkins.

Explain how to configure Slack notifications in Jenkins from start to finish.

Think about plugin installation, Slack setup, Jenkins configuration, and pipeline usage.

Describe how the 'slackSend' step works in a Jenkins pipeline script.

Focus on the command usage and its parameters.

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