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.