Email notification plugin in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the recipient email address in Jenkins email notification.

Jenkins

emailext(
  to: '[1]',
  subject: 'Build Notification',
  body: 'The build has completed.'
)

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

[e-mail]

[e-mail]

[e-mail]

[e-mail]

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid email format

Leaving the recipient field empty

The to field specifies the recipient email address. Here, [e-mail] is the correct recipient.

2fill in blank

medium

Complete the code to set the email subject line in Jenkins email notification.

Jenkins

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

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

A'Build Notification'

B'Build Status'

C'Build Complete'

D'Notification Email'

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the subject string

Using an unrelated subject line

The subject field sets the email subject line. 'Build Notification' clearly indicates the purpose.

3fill in blank

hard

Fix the error in the Jenkins email notification code by completing the missing field.

Jenkins

emailext(
  to: '[e-mail]',
  subject: 'Build Notification',
  body: [1]
)

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

AThe build has failed.

B'The build has failed.'

Cbuild_failed

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around the body text

Using undefined variables instead of strings

The body field must be a string enclosed in quotes. Option B correctly provides a string.

4fill in blank

hard

Fill both blanks to add a reply-to address and set the email content type in Jenkins email notification.

Jenkins

emailext(
  to: '[e-mail]',
  replyTo: '[1]',
  contentType: '[2]',
  subject: 'Build Notification',
  body: 'Build completed.'
)

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

[e-mail]

Btext/plain

Ctext/html

[e-mail]

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid email format for replyTo

Setting contentType to unsupported values

The replyTo field sets the reply address, here [e-mail]. The contentType is set to text/html to allow HTML content in the email body.

5fill in blank

hard

Fill all three blanks to configure a Jenkins email notification with recipient, subject, and body using variables.

Jenkins

def recipient = '[e-mail]'
def subjectLine = 'Build [1]'
def messageBody = 'The build number [2] has [3].'

emailext(
  to: recipient,
  subject: subjectLine,
  body: messageBody
)

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

AStatus

B#42

Csucceeded

Dfailed

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up build status words

Not using variables correctly in strings

The subject line uses 'Status' to describe the build state. The build number is '#42'. The body states the build 'succeeded'. This combination forms a clear notification.

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