This option adds a header to emails from Jenkins. As the help suggests, this can be useful with filtering and also avoiding autoresponders. Selecting this option allows you to apply a list-id header to all emails. General configuration for extended emailsДЄ few new fields deserve further explanation. The Email Extension plugin provides many additional options for expanding how emails are handled, but it also comes with trade-offs when using it in a pipeline environment.

While the built-in functionality covers the basic email needs, there may be times when you need or want to further customize and control the emails that Jenkins sends. If there is a successful build, this will look the same except FAILURE will be replaced with SUCCESS. Subject: Status of pipeline: pipeline2 #1

These pipelines will produce an email like the following if there is a failure: In this case, we are simply using the always clause for a generic demonstration. Note that, as described in ChapterВ 7, the post section supports separate processing for build statuses such as success, failure, etc. Next, weвЂ™ll look at the traditional settings for email notifications in Jenkins. Here, you can see the value of the вЂњSystem Admin e-mail addressвЂќ field in the X-Google-Original-From header: X-Received: by 10.55.93.197 with SMTP id r188mr35950021qkb.277.1502803051345 An example of deep-diving into those is shown next. In most cases, you likely wonвЂ™t see the admin address unless you dig into the headers for the email. In reality, for most purposes, the email address for the user (configured later) will be the one surfaced in the emails. So you will need to reference a clickable URL. However, this is the Jenkins URL that will appear in the links in emails sent from Jenkins. Note that this is optional, and you could leave it as something like вЂњlocalhost:8080вЂќ. The Jenkins URL field in this section provides a place to put in the more user-friendly name of your Jenkins system.

Hipchat download instructions