Email notifications in pipelines in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Email Notification Syntax in Jenkins Pipeline

What is the output when the following Jenkins pipeline snippet runs, assuming the email plugin is correctly configured and the build fails?

Jenkins

pipeline {
  agent any
  stages {
    stage('Failing Stage') {
      steps {
        script {
          error('Forced failure')
        }
      }
    }
  }
  post {
    failure {
      emailext(
        subject: "Build Failed: ${env.JOB_NAME} #${env.BUILD_NUMBER}",
        body: "The build failed. Check the console output at ${env.BUILD_URL}console",
        to: '[e-mail]'
      )
    }
  }
}

A An email is sent to [e-mail] with the subject 'Build Failed: <job_name> #<build_number>' and a body containing the build URL.

B No email is sent because the 'failure' block only triggers on success.

C The pipeline throws a syntax error due to missing parentheses in the emailext step.

D The email is sent but only if the build succeeds, not on failure.

💡 Hint

Check the 'post' section and the 'failure' condition in Jenkins pipelines.

The 'post' block with 'failure' triggers only when the build fails. The emailext step sends an email with the specified subject and body to the given recipient.

❓ Troubleshoot

intermediate

Troubleshooting Missing Email Notifications

A Jenkins pipeline uses the emailext step in the post section to send failure notifications. However, no emails are received even though the build fails. Which of the following is the most likely cause?

A The SMTP server is not configured or unreachable in Jenkins global settings.

B The pipeline script uses 'mail' instead of 'emailext' step.

C The 'post' block is placed inside the 'stages' block instead of directly under 'pipeline'.

D The 'failure' condition is misspelled as 'failuer' in the post block.

💡 Hint

Check Jenkins global configuration for email settings.

If the SMTP server is not set or unreachable, Jenkins cannot send emails even if the pipeline script is correct.

❓ Configuration

advanced

Configuring Email Recipients Dynamically

Which Jenkins pipeline snippet correctly sends an email notification to a dynamic list of recipients stored in a variable called 'emailList' when the build is unstable?

Jenkins

def emailList = '[e-mail],[e-mail]'

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        script {
          currentBuild.result = 'UNSTABLE'
        }
      }
    }
  }
  post {
    unstable {
      // Which option correctly sends email to emailList?
    }
  }
}

A emailext(to: '${emailList}', subject: 'Build Unstable', body: 'Check the build status.')

B emailext(to: "${emailList}", subject: 'Build Unstable', body: 'Check the build status.')

C emailext(to: emailList, subject: 'Build Unstable', body: 'Check the build status.')

D emailext(to: '$emailList', subject: 'Build Unstable', body: 'Check the build status.')

💡 Hint

Use Groovy string interpolation with double quotes for variables.

In Jenkins pipeline Groovy scripts, variables inside double quotes are interpolated. Single quotes or no quotes do not interpolate variables correctly.

🔀 Workflow

advanced

Email Notification Workflow with Multiple Conditions

In a Jenkins pipeline, you want to send an email notification only if the build is either unstable or failed, but not on success or aborted. Which post block configuration achieves this?

A

post {
  failure, unstable {
    emailext(to: '[e-mail]', subject: 'Build Alert', body: 'Check build')
  }
}

B

post {
  always {
    script {
      if (currentBuild.result == 'FAILURE' || currentBuild.result == 'UNSTABLE') {
        emailext(to: '[e-mail]', subject: 'Build Alert', body: 'Check build')
      }
    }
  }
}

C

post {
  failure {
    emailext(to: '[e-mail]', subject: 'Build Failed', body: 'Check build')
  }
  unstable {
    emailext(to: '[e-mail]', subject: 'Build Unstable', body: 'Check build')
  }
}

D

post {
  changed {
    emailext(to: '[e-mail]', subject: 'Build Changed', body: 'Check build')
  }
}

💡 Hint

Use separate blocks for failure and unstable conditions.

Jenkins pipeline post blocks support separate conditions like failure and unstable. Combining them in one block with a comma is invalid syntax.

✅ Best Practice

expert

Best Practice for Sensitive Email Credentials in Jenkins Pipelines

What is the best practice to securely use SMTP credentials for sending email notifications in Jenkins pipelines?

A Hardcode SMTP username and password directly in the pipeline script for easy access.

B Use environment variables set on the Jenkins master node without encryption.

C Store SMTP credentials in a plain text file inside the repository and read them during the pipeline.

D Store SMTP username and password as Jenkins credentials and reference them in the pipeline using withCredentials block.

💡 Hint

Consider Jenkins secure credentials management features.

Using Jenkins credentials store with withCredentials block keeps sensitive data encrypted and avoids exposing secrets in code or logs.

Practice

1. What is the main purpose of adding email notifications in Jenkins pipelines?

easy

A. To increase the number of pipeline stages

B. To speed up the pipeline execution

C. To automatically inform team members about pipeline success or failure

D. To reduce the size of the pipeline script

Solution

1. Step 1: Understand the role of email notifications

   Email notifications are used to keep team members informed about the status of the pipeline automatically.

2. Step 2: Identify the correct purpose

   Speeding up execution, increasing stages, or reducing script size are unrelated to email notifications.

3. Final Answer:

   To automatically inform team members about pipeline success or failure -> Option C

4. Quick Check:

   Email notifications = Inform team automatically [OK]

Hint: Email notifications alert teams about pipeline results [OK]

Common Mistakes:

• Thinking email notifications speed up pipelines
• Confusing notifications with pipeline structure changes
• Assuming notifications reduce script size

2. Which Jenkins pipeline syntax correctly sends an email notification only on failure using the post section?

easy

A. post { failure { emailext to: '[e-mail]', subject: 'Build Failed', body: 'Check the logs.' } }

B. post { always { emailext to: '[e-mail]', subject: 'Build Failed', body: 'Check the logs.' } }

C. post { success { emailext to: '[e-mail]', subject: 'Build Failed', body: 'Check the logs.' } }

D. post { failure { mail to: '[e-mail]', subject: 'Build Failed', body: 'Check the logs.' } }

Solution

1. Step 1: Identify correct post condition for failure

   The failure block runs only when the pipeline fails, which is correct here.

2. Step 2: Check the email sending syntax

   emailext is the correct step for sending emails with extended options; mail is less common and may lack features.

3. Final Answer:

   post { failure { emailext to: '[e-mail]', subject: 'Build Failed', body: 'Check the logs.' } } -> Option A

4. Quick Check:

   Failure + emailext = Correct syntax [OK]

Hint: Use 'post { failure { emailext ... } }' for failure emails [OK]

Common Mistakes:

• Using 'always' instead of 'failure' for failure-only emails
• Using 'success' block for failure notifications
• Using 'mail' instead of 'emailext' without plugin support

3. Given this Jenkins pipeline snippet, what will happen when the build succeeds?

post {
  success {
    emailext to: '[e-mail]', subject: 'Build Success', body: 'Good job!'
  }
  failure {
    emailext to: '[e-mail]', subject: 'Build Failed', body: 'Please check.'
  }
}

medium

A. Both success and failure emails are sent

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

C. No email is sent

D. An email with subject 'Build Success' is sent to [e-mail]

Solution

1. Step 1: Understand post conditions for success

   The success block triggers only when the build finishes successfully.

2. Step 2: Identify which email is sent on success

   The email with subject 'Build Success' is sent to '[e-mail]' in the success block.

3. Final Answer:

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

4. Quick Check:

   Success block sends success email [OK]

Hint: Success block emails only on successful builds [OK]

Common Mistakes:

• Confusing failure email with success email
• Thinking no email is sent on success
• Assuming both emails send regardless of build result

4. You wrote this Jenkins pipeline snippet to send failure emails, but no emails are sent on failure:

post {
  failure {
    mail to: '[e-mail]', subject: 'Build Failed', body: 'Fix it!'
  }
}

What is the likely problem?

medium

A. The 'failure' block should be 'always' to send emails on failure

B. The 'mail' step requires proper configuration; use 'emailext' instead

C. The 'to' field must be inside quotes like "to: '[e-mail]'"

D. The 'body' field is missing a required parameter

Solution

1. Step 1: Check the email step used

   The mail step is basic and may not work without proper setup; emailext from the Email Extension plugin is recommended for reliable emails.

2. Step 2: Confirm correct step for failure emails

   Using emailext ensures emails are sent with more options and better support in pipelines.

3. Final Answer:

   The 'mail' step requires proper configuration; use 'emailext' instead -> Option B

4. Quick Check:

   Use emailext for failure emails [OK]

Hint: Use 'emailext' not 'mail' for reliable email notifications [OK]

Common Mistakes:

• Using 'mail' without proper configuration
• Confusing 'failure' with 'always' block
• Incorrect quoting of parameters

5. You want to send an email notification only if the build fails and the failure is caused by a test failure. Which Jenkins pipeline snippet correctly implements this logic?

hard

A. post {
failure {
script {
if (currentBuild.rawBuild.getLog(100).any { it.contains('TEST-FAILURE') }) {
emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!'
}
}
}
}

B. post {
always {
emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!'
}
}

C. post {
failure {
emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!'
}
}

D. post {
success {
emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!'
}
}

Solution

1. Step 1: Understand the requirement for conditional email on test failure

   The email should send only if the build fails and the failure is due to test failures, so a condition checking the build log is needed.

2. Step 2: Analyze the options for conditional logic

   post { failure { script { if (currentBuild.rawBuild.getLog(100).any { it.contains('TEST-FAILURE') }) { emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!' } } } } uses a script block to check the build log for 'TEST-FAILURE' text before sending the email, matching the requirement exactly.

3. Step 3: Exclude other options

   post { always { emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!' } } sends email always, ignoring failure condition. post { failure { emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!' } } sends email on any failure, not just test failures. post { success { emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!' } } sends email on success, which is incorrect.

4. Final Answer:

   post { failure { script { if (currentBuild.rawBuild.getLog(100).any { it.contains('TEST-FAILURE') }) { emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!' } } } } -> Option A

5. Quick Check:

   Conditional script in failure block = post { failure { script { if (currentBuild.rawBuild.getLog(100).any { it.contains('TEST-FAILURE') }) { emailext to: '[e-mail]', subject: 'Test Failure', body: 'Tests failed!' } } } } [OK]

Hint: Use script block to check logs inside failure post section [OK]

Common Mistakes:

• Sending emails on all failures without checking cause
• Using 'always' or 'success' blocks incorrectly
• Not using script block for conditional logic