{"id":437,"date":"2026-10-14T09:31:29","date_gmt":"2026-10-14T09:31:29","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2015\/10\/03\/how-to-attach-the-jenkins-build-log-as-part-of-the-email-body-2\/"},"modified":"2026-10-14T09:31:29","modified_gmt":"2026-10-14T09:31:29","slug":"how-to-attach-the-jenkins-build-log-as-part-of-the-email-body-2","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/how-to-attach-the-jenkins-build-log-as-part-of-the-email-body-2\/","title":{"rendered":"Jenkins Email-ext: Add Full or Regex-Filtered Build Logs to Email Body"},"content":{"rendered":"\n

Originally published on 2015-10-03; fully revised and updated.<\/em><\/p>\n\n\n\n

If your team depends on Jenkins email alerts, putting the right build-log content in the email body can speed up incident triage. This guide explains how to use Email Extension (email-ext) content tokens for full logs and regex-filtered snippets, plus practical examples you can copy into job configuration or Pipeline.<\/p>\n\n\n

\n
\"Jenkins<\/figure>\n<\/div>\n\n\n

Choose the right log-in-email strategy<\/h2>\n\n\n\n

There are two common approaches: include the whole log, or include only matched lines (with context). The second option keeps emails concise when builds produce large output.<\/p>\n\n\n\n

Token or link<\/th>What it adds to the email<\/th>Best for<\/th>Trade-off<\/th><\/tr><\/thead>
${BUILD_LOG, maxLines=9999, escapeHtml=false}<\/code><\/td>Full (or near-full) build console output<\/td>Small\/medium logs, immediate context<\/td>Can create very long and noisy emails<\/td><\/tr>
${BUILD_LOG_REGEX, ...}<\/code><\/td>Only lines matching a regex, optionally with lines before\/after<\/td>Failure summaries, error-first notifications<\/td>Needs careful regex tuning<\/td><\/tr>
${BUILD_URL}\/artifact\/<\/code><\/td>Link to build artifacts<\/td>Reports, logs, packaged outputs<\/td>Requires Jenkins access and artifact retention<\/td><\/tr>
${PROJECT_URL}\/ws\/<\/code><\/td>Link to workspace<\/td>Quick inspection in trusted\/internal environments<\/td>May be inaccessible or restricted by security settings<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

How email-ext token rendering works in notifications<\/h2>\n\n\n\n

When a job trigger fires an email-ext notification, Jenkins resolves tokens in the subject\/body and injects log content based on token parameters.<\/p>\n\n\n\n

\nflowchart TD\n    A[Build runs in Jenkins] --> B[Email trigger condition met]\n    B --> C[email-ext composes message]\n    C --> D{Token used in body}\n    D --> E[BUILD_LOG inserts full log]\n    D --> F[BUILD_LOG_REGEX filters by pattern]\n    E --> G[Email sent to recipients]\n    F --> G\n    G --> H[Team triages result]\n<\/pre>\n\n\n\n
Way 1: Include the full build log in the email body<\/h2>\n\n\n\n
For freestyle-style configuration, place a BUILD_LOG<\/code> token in the email-ext content field (for example, in Default Content or job-level editable email content).<\/p>\n\n\n\n