Why notifications matter in Jenkins - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send an email notification after a Jenkins build.

Jenkins

post {
  always {
    emailext [1] {
      to: '[e-mail]'
      subject: 'Build Notification'
      body: 'The build has completed.'
    }
  }
}

Drag options to blanks, or click blank then click option'

Amail

Bnotify

Cemail

Dsend

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'notify' instead of 'send' causes a syntax error.

Using 'mail' is a different step and not part of emailext.

The emailext send step triggers the email notification in Jenkins pipelines.

2fill in blank

medium

Complete the code to notify only when the build fails.

Jenkins

post {
  [1] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build Failed'
      body: 'Please check the build logs.'
    }
  }
}

Drag options to blanks, or click blank then click option'

Asuccess

Balways

Cfailure

Dunstable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'always' sends notifications every time.

Using 'success' sends notifications only on success.

The failure block runs only when the build fails, triggering the notification.

3fill in blank

hard

Fix the error in the notification block to correctly send an email on unstable builds.

Jenkins

post {
  unstable {
    emailext [1] {
      to: '[e-mail]'
      subject: 'Build Unstable'
      body: 'The build is unstable.'
    }
  }
}

Drag options to blanks, or click blank then click option'

Asend

Bnotify

Cemail

Dmail

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'notify' or 'email' causes the pipeline to fail.

Using 'mail' is a different plugin step.

The correct step to send emails with the emailext plugin is send.

4fill in blank

hard

Fill both blanks to send notifications only when the build is successful and unstable.

Jenkins

post {
  [1] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build Success'
      body: 'The build succeeded.'
    }
  }
  [2] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build Unstable'
      body: 'The build is unstable.'
    }
  }
}

Drag options to blanks, or click blank then click option'

Asuccess

Bfailure

Cunstable

Dalways

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'failure' instead of 'success' sends notifications on failure.

Using 'always' sends notifications every time.

The success block runs on successful builds, and unstable runs on unstable builds, sending notifications accordingly.

5fill in blank

hard

Fill all three blanks to send notifications with dynamic subject and body based on build status.

Jenkins

post {
  [1] {
    emailext send {
      to: '[e-mail]'
      subject: 'Build [2]'
      body: 'The build status is [3].'
    }
  }
}

Drag options to blanks, or click blank then click option'

Afailure

Bsuccess

CFAILED

DSUCCESS

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing failure block with success messages.

Using lowercase status words in subject and body.

When the build is successful, the success block runs, and the subject and body reflect the success status.

Practice

1. Why are notifications important in Jenkins pipelines?

easy

A. They increase the build time significantly.

B. They slow down the pipeline execution.

C. They delete old build logs automatically.

D. They alert the team about pipeline successes or failures quickly.

Solution

1. Step 1: Understand the purpose of notifications

   Notifications inform the team about important events like build success or failure.

2. Step 2: Identify the benefit of quick alerts

   Quick alerts help the team react fast to fix issues or celebrate success.

3. Final Answer:

   They alert the team about pipeline successes or failures quickly. -> Option D

4. Quick Check:

   Notifications = Quick alerts [OK]

Hint: Notifications = Fast alerts about pipeline status [OK]

Common Mistakes:

• Thinking notifications slow down builds
• Confusing notifications with log cleanup
• Believing notifications increase build time

2. Which Jenkins plugin is commonly used to send notifications to Slack?

easy

A. Email Extension Plugin

B. Slack Notification Plugin

C. Git Plugin

D. Docker Plugin

Solution

1. Step 1: Identify notification plugins in Jenkins

   Jenkins has specific plugins for different notification methods.

2. Step 2: Match Slack notifications to the correct plugin

   The Slack Notification Plugin is designed to send messages to Slack channels.

3. Final Answer:

   Slack Notification Plugin -> Option B

4. Quick Check:

   Slack notifications = Slack Notification Plugin [OK]

Hint: Slack notifications use Slack Notification Plugin [OK]

Common Mistakes:

• Choosing Email Extension Plugin for Slack
• Confusing Git Plugin with notification plugins
• Selecting unrelated plugins like Docker Plugin

3. Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
  post {
    failure {
      mail to: '[e-mail]', subject: 'Build Failed', body: 'Please check the build.'
    }
  }
}

What happens when the build fails?

medium

A. An email is sent to [e-mail] notifying the failure.

B. The pipeline retries the build automatically.

C. The build logs are deleted.

D. Nothing happens; no notification is sent.

Solution

1. Step 1: Analyze the post-failure block in the pipeline

   The post block with failure condition sends an email with specified details.

2. Step 2: Understand the email step

   The mail step sends an email to '[e-mail]' with subject and body on failure.

3. Final Answer:

   An email is sent to [e-mail] notifying the failure. -> Option A

4. Quick Check:

   Failure triggers email notification [OK]

Hint: Post failure block sends email notification [OK]

Common Mistakes:

• Assuming automatic retry on failure
• Thinking logs get deleted on failure
• Believing no notification is sent

4. You added this notification step in Jenkins:

post {
  success {
    slackSend channel: '#dev', message: 'Build succeeded!'
  }
}

But no Slack message is sent after a successful build. What is the likely cause?

medium

A. Slack messages only send on failure, not success.

B. The pipeline syntax is incorrect and causes failure.

C. Slack plugin is not installed or configured properly.

D. The channel name must start with '@' not '#'.

Solution

1. Step 1: Check plugin installation and configuration

   Slack notifications require the Slack plugin installed and configured with credentials.

2. Step 2: Verify syntax and channel format

   The syntax is correct and channel names start with '#', so these are not the issue.

3. Final Answer:

   Slack plugin is not installed or configured properly. -> Option C

4. Quick Check:

   No Slack message = Plugin/config issue [OK]

Hint: Check Slack plugin and config if no messages sent [OK]

Common Mistakes:

• Assuming syntax error without checking plugin
• Thinking Slack only sends failure messages
• Confusing channel prefix '@' with '#'

5. You want Jenkins to notify your team only when a build fails twice in a row. Which approach best achieves this?

hard

A. Use a plugin or script to track consecutive failures and send notification only after two failures.

B. Send notifications on every build success and failure.

C. Disable notifications and check build status manually.

D. Send notifications only on the first failure, ignoring subsequent failures.

Solution

1. Step 1: Understand the requirement for consecutive failure notifications

   Notifications should trigger only after two failures in a row, not every failure.

2. Step 2: Identify how to track consecutive failures

   Using a plugin or custom script can track build history and send notifications accordingly.

3. Final Answer:

   Use a plugin or script to track consecutive failures and send notification only after two failures. -> Option A

4. Quick Check:

   Consecutive failure alert = Plugin/script tracking [OK]

Hint: Track consecutive failures with plugin/script for notifications [OK]

Common Mistakes:

• Sending notifications on every build regardless
• Ignoring the need to track failure history
• Disabling notifications and missing alerts