Email notification plugin in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Email Notification Plugin - Default Behavior

What is the output in Jenkins console log when the Email Notification plugin is configured but the SMTP server is unreachable during a build?

A Build fails with error: Could not connect to SMTP host

B Build succeeds but email is silently dropped

C Build succeeds and email is queued for retry

D Build fails with error: Email plugin not installed

💡 Hint

Think about what happens when Jenkins tries to send email but cannot reach the SMTP server.

When the SMTP server is unreachable, the Email Notification plugin logs a connection error like 'Could not connect to SMTP host' and the build fails.

❓ Configuration

intermediate

Configuring SMTP Server in Jenkins Email Notification Plugin

Which configuration snippet correctly sets the SMTP server to smtp.example.com with port 587 and enables STARTTLS in Jenkins Email Notification plugin's global configuration?

A

smtpServer=smtp.example.com
smtpPort=25
useSsl=true
useStartTls=false

B

smtpServer=smtp.example.com
smtpPort=587
useSsl=true
useStartTls=false

C

smtpServer=smtp.example.com
smtpPort=465
useSsl=false
useStartTls=true

D

smtpServer=smtp.example.com
smtpPort=587
useSsl=false
useStartTls=true

💡 Hint

STARTTLS usually runs on port 587 and requires useStartTls=true with useSsl=false.

Port 587 with STARTTLS enabled (useStartTls=true) and SSL disabled (useSsl=false) is the correct setup for SMTP with STARTTLS.

🔀 Workflow

advanced

Email Notification Plugin - Conditional Email Sending

In a Jenkins pipeline, which scripted step correctly sends an email only if the build status is FAILURE using the Email Notification plugin?

A if (currentBuild.result == 'FAILURE') { emailext subject: 'Build Failed', body: 'Check logs', to: '[e-mail]' }

B if (buildStatus == 'FAILURE') { emailext subject: 'Build Failed', body: 'Check logs', to: '[e-mail]' }

C if (currentBuild.currentResult == 'FAILURE') { emailext subject: 'Build Failed', body: 'Check logs', to: '[e-mail]' }

D if (currentBuild.status == 'FAILURE') { emailext subject: 'Build Failed', body: 'Check logs', to: '[e-mail]' }

💡 Hint

The correct property to check current build status is currentBuild.currentResult.

In Jenkins scripted pipeline, currentBuild.currentResult holds the build status. Using it in the if condition correctly triggers email on failure.

❓ Troubleshoot

advanced

Diagnosing Email Notification Plugin Failure

A Jenkins job configured with Email Notification plugin does not send emails, but the build succeeds. Which log message indicates the root cause?

A Error: SMTP authentication failed

B Warning: No recipients specified for email notification

C Info: Email sent successfully

D Error: Plugin not found

💡 Hint

If no email addresses are set, the plugin skips sending emails without failing the build.

The warning 'No recipients specified for email notification' means the plugin has no target addresses, so it skips sending emails silently.

✅ Best Practice

expert

Best Practice for Securing SMTP Credentials in Jenkins Email Notification Plugin

What is the recommended way to securely manage SMTP credentials for the Jenkins Email Notification plugin to avoid exposing passwords in job configurations?

A Store SMTP username and password in Jenkins Credentials plugin and reference them in the Email Notification configuration

B Hardcode SMTP username and password directly in the Jenkins job configuration

C Use environment variables in the Jenkins job to store SMTP credentials in plain text

D Save SMTP credentials in a text file on the Jenkins master and read them in the job

💡 Hint

Jenkins Credentials plugin is designed to securely store secrets.

Using Jenkins Credentials plugin to store SMTP credentials keeps them encrypted and avoids exposing passwords in job configs or logs.

Practice

1. What is the main purpose of the Jenkins Email Notification plugin?

easy

A. To deploy applications to servers

B. To automatically send emails about build status

C. To monitor server CPU usage

D. To create new Jenkins jobs

Solution

1. Step 1: Understand the plugin's function

   The Email Notification plugin is designed to send emails automatically when a build finishes.

2. Step 2: Identify the correct purpose

   It helps keep the team informed by sending build status emails without manual effort.

3. Final Answer:

   To automatically send emails about build status -> Option B

4. Quick Check:

   Email Notification plugin = automatic build emails [OK]

Hint: Email plugin = auto send build status emails [OK]

Common Mistakes:

• Confusing with deployment tools
• Thinking it monitors server health
• Assuming it creates jobs

2. Which of the following is the correct syntax to enable email notifications in a Jenkins pipeline script?

easy

A. sendEmail(subject: 'Build Status', body: 'Build completed', to: '[e-mail]')

B. emailNotify(subject: 'Build Status', body: 'Build completed', to: '[e-mail]')

C. emailext(subject: 'Build Status', body: 'Build completed', to: '[e-mail]')

D. notifyEmail(subject: 'Build Status', body: 'Build completed', to: '[e-mail]')

Solution

1. Step 1: Recall Jenkins pipeline email syntax

   The Email Extension plugin uses the emailext step to send emails.

2. Step 2: Match the correct function name and parameters

   Only emailext(subject: 'Build Status', body: 'Build completed', to: '[e-mail]') uses emailext with correct parameters: subject, body, and to.

3. Final Answer:

   emailext(subject: 'Build Status', body: 'Build completed', to: '[e-mail]') -> Option C

4. Quick Check:

   Use emailext for email notifications [OK]

Hint: Use 'emailext' step for Jenkins email notifications [OK]

Common Mistakes:

• Using incorrect function names
• Missing required parameters
• Confusing with other plugins

3. Given this Jenkins pipeline snippet:

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

What happens if the build fails?

medium

A. An email with subject 'Build Failed' is sent to [e-mail]

B. No email is sent because the syntax is wrong

C. An email is sent only if the build succeeds

D. The build will retry automatically

Solution

1. Step 1: Analyze the post-failure block

   The post { failure { ... } } block runs only if the build fails.

2. Step 2: Understand the emailext usage

   The emailext step sends an email with the given subject and body to the specified address.

3. Final Answer:

   An email with subject 'Build Failed' is sent to [e-mail] -> Option A

4. Quick Check:

   Post failure triggers email = An email with subject 'Build Failed' is sent to [e-mail] [OK]

Hint: Post failure block sends email on build failure [OK]

Common Mistakes:

• Thinking email sends on success
• Assuming syntax error without checking
• Confusing retry with email notification

4. You configured the Email Notification plugin but no emails are sent after build failures. Which is the most likely cause?

medium

A. SMTP server settings are missing or incorrect

B. The Jenkins job has no build steps

C. The build always succeeds

D. The plugin is not installed

Solution

1. Step 1: Check email sending prerequisites

   Jenkins needs correct SMTP server settings to send emails.

2. Step 2: Identify common misconfiguration

   If SMTP settings are missing or wrong, emails won't send even if plugin is configured.

3. Final Answer:

   SMTP server settings are missing or incorrect -> Option A

4. Quick Check:

   SMTP config missing = no emails sent [OK]

Hint: Verify SMTP settings to fix email sending issues [OK]

Common Mistakes:

• Ignoring SMTP configuration
• Assuming plugin auto-configures SMTP
• Thinking build steps affect email sending

5. You want to send an email notification only when the build status changes (e.g., from success to failure or failure to success). Which Email Notification plugin feature should you use?

hard

A. Use the 'Send e-mail for every unstable build' option

B. Use the 'Always send e-mail' option

C. Configure a post-build script to check status manually

D. Enable 'Send e-mail only on status change' in the plugin settings

Solution

1. Step 1: Understand the requirement

   The goal is to send emails only when build status changes, not every build.

2. Step 2: Identify plugin feature for status change

   The Email Notification plugin has an option named 'Send e-mail only on status change' to handle this.

3. Step 3: Compare other options

   Options A and D send emails more frequently; Configure a post-build script to check status manually requires manual scripting.

4. Final Answer:

   Enable 'Send e-mail only on status change' in the plugin settings -> Option D

5. Quick Check:

   Status change emails = enable plugin's status change option [OK]

Hint: Enable 'send only on status change' to reduce email noise [OK]

Common Mistakes:

• Choosing options that send emails every build
• Ignoring built-in plugin features
• Overcomplicating with manual scripts