Configuring Email Notifications in Jenkins (Basic and Advanced)

Jenkins can send build status emails to keep developers and operations informed. There are two ways to configure email notifications: a basic method through System Management → System Configuration → Mail Notification (system administrator email address) and an advanced method using the Extended E‑mail Notification plugin.

In most deployment workflows, test environments are open for developers, while pre‑production environments require test approval and an email notification to operations before deployment. To avoid missed notifications, configuring Jenkins to automatically send build emails is essential.

1. Global Configuration

Navigate to System Management → System Settings and locate Extended E‑mail Notification . Fill in the SMTP server details, enable advanced SMTP authentication, and provide the sender's username and password. Specify default recipients (separate multiple addresses with spaces) and click the "Default Triggers..." button to select which events should trigger email alerts, such as build failures or unstable builds. Save the global settings before proceeding to project‑level configuration.

Configure the mail address and password for the sender.

Set the default triggers so that build failures or abnormal status codes generate email alerts.

Below is the basic system mail configuration screenshot.

2. Project Configuration

Open the specific project's configuration page, click Configure , then add a post‑build action called Editable Email Notification . Save the default settings, or use Advanced Settings to customize recipients, subject, content, attachments, and other options for that project.

After saving, trigger a test build to verify that the configured email address receives the notification.

A successful test build shows no email is sent.

A failed test build (e.g., due to a wrong command) triggers an email notification.