Skip to main content
Jenkins offers an integrated email notification feature that lets you alert teams on build status changes—failures, unstable builds, or when a build returns to normal. You can configure notifications at both the individual job level and in the global Jenkins settings for consistent alerting across all jobs. Below is a quick overview of the built-in notification triggers:
TriggerDescription
FailureSends emails whenever a build fails
UnstableNotifies stakeholders when a build is unstable
Back to normalAlerts the team when a previously failing build succeeds
CulpritsEmails users identified as responsible for build failures

​
1. Enable Email Notification in a Job

  1. In Jenkins, open the npm-version-test job and click Configure.
  2. Scroll to Post-build Actions and search for Email Notification.
  3. Select Email Notification and enter recipient addresses (e.g., your Gmail). Optionally, enable Send separate emails to culprits for direct notifications.
  4. Click Apply to save.
The image shows a Jenkins configuration screen for a project named "npm-version-test," focusing on the "Post-build Actions" section where email notifications are set up for build status updates.
To force a failure and test the email trigger, add the following to your build steps: 
echo "Updating job config using Jenkins CLI"
npm -v
node -v
exit 1
Run the job again. You should see the build fail (e.g., Build #9):
The image shows a Jenkins dashboard for a project named "npm-version-test," displaying build history and permalinks for recent builds. The interface includes options like "Build Now," "Configure," and "Delete Project."
In the console log, you’ll encounter: 
ERROR: Couldn't connect to host, port: localhost, 25; timeout 60000
org.eclipse.angus.mail.util.MailConnectException: ...
By default, Jenkins uses localhost:25 for SMTP. Unless you run a local mail server, this will fail. Configure a valid SMTP host and port in the global settings to resolve this.

​
2. Configure Global SMTP Settings

  1. Go to Manage Jenkins → Configure System.
  2. Scroll to Extended E-mail Notification (or Email Notification) and fill in:
    FieldValue
    SMTP serversmtp.gmail.com
    Default user e-mail suffix(leave blank)
    Use SMTP Authentication☑
    Use SSL☑
    User Name[email protected]
    Password(Gmail app password)
    SMTP Port465
The image shows the email notification configuration settings in Jenkins, with fields for SMTP server, default user email suffix, and options for SMTP authentication, SSL, and TLS.
  1. Click Test Configuration:
The image shows a configuration screen in Jenkins for setting up SMTP email settings, including fields for username, password, SSL, and SMTP port.
jakarta.mail.AuthenticationFailedException: 534-5.7.9 Application-specific password required ...
Gmail no longer accepts regular account passwords for SMTP. You must generate an app-specific password if Two-Factor Authentication (2FA) is enabled.

​
3. Generate a Gmail App Password

  1. Sign in to your Google Account and navigate to Security.
  2. Ensure 2-Step Verification is enabled.
  3. Under App passwords, click Select app → Other (Custom name), name it (e.g., “Jenkins email service”), then Generate.
The image shows a Google Account page for managing app passwords, with existing passwords listed and an option to create a new app-specific password named "jenkins-email."
  1. Copy the 16-character app password.
The image shows a Google Account page with a pop-up displaying a generated app password and instructions on how to use it.
  1. Replace the SMTP Password in Jenkins with the new app password and click Test Configuration again. You should see a success:
The image shows a Gmail inbox with an email titled "Test email #2" from a sender associated with Jenkins. The email content mentions it is a test email sent from Jenkins.

​
4. Set System Admin Email Address

To customize the “From” address on outgoing alerts:
  1. In Manage Jenkins → Configure System, set System Admin e-mail address (e.g., [email protected]).
  2. Click Save and then Test Configuration once more.
The image shows a Jenkins configuration page where the user is setting the Jenkins URL and the system admin email address. There is a warning to set a valid host name instead of "localhost."
You’ll receive another test email showing the updated From address:
The image shows a Gmail interface with an open email labeled "Test email #3" from "sid demos." A contact card is displayed, showing options to send mail and view details.

​
5. Verify Notifications on Job Builds

  1. Return to the npm-version-test job and rebuild with the same exit 1 script.
  2. Build #10 will fail and trigger an email:
The image shows a Jenkins dashboard for a project named "npm-version-test," displaying build history and permalinks for recent builds. The sidebar includes options like "Build Now," "Configure," and "Delete Project."
Console Output: 
Started by user siddharth
...
+ exit 1
Build step 'Execute shell' marked build as failure
Sending e-mails to: [email protected]
Finished: FAILURE
You’ll receive an email titled Build failed in Jenkins: npm-version-test #10, complete with console logs and direct links:
The image shows an email notification in Gmail about a Jenkins build failure for "npm-version-test #10," including details of the build process and error message.
Finally, remove the exit 1 from the build script and run again. Build #11 will succeed and send a “back to normal” message without console logs, confirming your notification pipeline is fully operational.

Watch Video