Hi Neil, I have as example the following content in the global setup of email- ext:
------------- SNIP ------------------ $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS: Check console output at $BUILD_URL or see build log below to view the results. Changes since last build: $CHANGES ---------------------------------------------------------------------------------------------------- Build log (last 250 lines): $BUILD_LOG ------------- SNAP ------------------ And that result into: ------------- SNIP ------------------ MB_GUIDE - Build # 85 - Failure: Check console output at http://b00012:8080/job/MB_GUIDE/85/ or see build log below to view the results. Changes since last build: ---------------------------------------------------------------------------------------------------- Build log (last 250 lines): [...truncated 4591 lines...] U guide_NOT_FOR_YOU/speller_arrow_right.png U guide_NOT_FOR_YOU/speller_charset_toggle.png ---- something in between ---- U guide_NOT_FOR_YOU/tp3_orange.png U guide_NOT_FOR_YOU/tp_orange.png Determine Guide version - try versions 33 and 41 - report error of NONE exists D:\work\guide_NOT_FOR_YOU>set GUIDE_VERSION_SHORT=NONE D:\work\guide_NOT_FOR_YOU>if exist GUIDE_33_UPDATE.bat set GUIDE_VERSION_SHORT=33 D:\work\guide_NOT_FOR_YOU>if exist GUIDE_41_UPDATE.bat set GUIDE_VERSION_SHORT=41 D:\work\guide_NOT_FOR_YOU>if exist GUIDE_44_UPDATE.bat set GUIDE_VERSION_SHORT=44 D:\work\guide_NOT_FOR_YOU>if "NONE" == "NONE" exit /B 1 Build step 'Execute Windows batch command' marked build as failure Archiving artifacts Description set: NOT_FOR_YOU Email was triggered for: Failure Sending email for trigger: Failure BRANCH_NAME=NOT_FOR_YOU GUIDE_DB_AND_MODEL="NOT_FOR_YOU" BUILD_VARIANT=NOT_FOR_YOU GUIDE_TAG_USER_CHOICE=default GUIDE_TAG_USER_TEXT= ------------- SNAP ------------------ Take care Jan On 4 Apr., 10:25, Neil Bird <n...@fnxweb.com> wrote: > Around about 04/04/12 09:17, Neil Bird typed ... > > > Maybe I'm misunderstanding what Email-Ext does; I read it that it > > extends the built in email functionality. So, where I already have email > > set up (e.g., this test job), and then tick “Editable Email Notification”, I > > get the Email-Ext customisations for me emails. > > OK, that was it: Email-Ext doesn't extend the standard emails in the way > I interpreted, but replaces it. > > Under that misunderstanding, I had misinterpreted the job's config. > option “$DEFAULT_RECIPIENTS” as being the recipients I had listed above it > for the standard Jenkins emails. This must refer to the global config. > option. > > By adding my email address again explicitly to the Email-Ext recipient > list, I do indeed now get two emails, and the Email-Ext one is customised > somewhat as I expected. > > So all I have to do now is figure out how to make the email's body match > what Jenkins usually sets it to (as in, include the last bit of the job > output). > > Thanks for the pointers. > > -- > [neil@fnx ~]# rm -f .signature > [neil@fnx ~]# ls -l .signature > ls: .signature: No such file or directory > [neil@fnx ~]# exit
