Can't get email-ext plugin to work

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Can't get email-ext plugin to work

Neil Bird

   I have Jenkins 1.457 (Linux) and Email Extension Plugin 2.19 .

   I've ticked (and set) “Use List-ID Email Header” and “Add 'Precedence:
bulk' Email Header” in the main Jenkins config. (but not “Override Global
Settings”.

   In a number of projects I've then ticked “Editable Email Notification”
(and left everything else as defaults.)

   But I see no sign of any changes in their emails.


   What have I missed?

--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit

Reply | Threaded
Open this post in threaded view
|

Re: Can't get email-ext plugin to work

slide
Please give us a bit more information. What are you expecting? What
are you getting instead? Screenshots of your setup will help as well.

Thanks,

slide

On Tue, Apr 3, 2012 at 8:55 AM, Neil Bird <[hidden email]> wrote:

>
>  I have Jenkins 1.457 (Linux) and Email Extension Plugin 2.19 .
>
>  I've ticked (and set) “Use List-ID Email Header” and “Add 'Precedence:
> bulk' Email Header” in the main Jenkins config. (but not “Override Global
> Settings”.
>
>  In a number of projects I've then ticked “Editable Email Notification” (and
> left everything else as defaults.)
>
>  But I see no sign of any changes in their emails.
>
>
>  What have I missed?
>
> --
> [neil@fnx ~]# rm -f .signature
> [neil@fnx ~]# ls -l .signature
> ls: .signature: No such file or directory
> [neil@fnx ~]# exit
>



--
Website: http://earl-of-code.com
Reply | Threaded
Open this post in threaded view
|

Re: Can't get email-ext plugin to work

Neil Bird
Around about 03/04/12 17:30, Slide typed ...
> Please give us a bit more information. What are you expecting? What
> are you getting instead? Screenshots of your setup will help as well.

   As a minimum, I was hoping to see the extra headers I said I selected,
List-Id: and Precedence:, but neither are present in the emails.

   I've not tested changing the body of the email, I'll try that next as a
more obvious proof.


   I've attached a snippets of my global config. and one of the failing job
configs.

--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit

global-config.png (39K) Download Attachment
job-config.png (40K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Can't get email-ext plugin to work

Matthew.Webber
If all you do in your job config is tick the "Editable email notification" option, then it only sends an email on failure (not unstable). Is that the email you are getting?

If you look at the console log for any job, then right at the bottom, you can see what emails were sent. That might help.

Matthew
 

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Neil
> Bird
> Sent: 04 April 2012 08:50
> To: [hidden email]
> Cc: Slide
> Subject: Re: Can't get email-ext plugin to work
>
> Around about 03/04/12 17:30, Slide typed ...
> > Please give us a bit more information. What are you expecting? What
> > are you getting instead? Screenshots of your setup will help as well.
>
>    As a minimum, I was hoping to see the extra headers I said I selected,
> List-Id: and Precedence:, but neither are present in the emails.
>
>    I've not tested changing the body of the email, I'll try that next as a
> more obvious proof.
>
>
>    I've attached a snippets of my global config. and one of the failing job
> configs.
>
> --
> [neil@fnx ~]# rm -f .signature
> [neil@fnx ~]# ls -l .signature
> ls: .signature: No such file or directory
> [neil@fnx ~]# exit
Reply | Threaded
Open this post in threaded view
|

Re: Can't get email-ext plugin to work

Neil Bird
Around about 04/04/12 09:05, [hidden email] typed ...
> If all you do in your job config is tick the "Editable email notification"
> option, then it only sends an email on failure (not unstable). Is that the
> email you are getting?

   Yes;  I've set up a test job that just fails and is configured to email
me.  I get that email (and that is reported in the job output).  I added
some lines to the “Default Content” after $DEFAULT_CONTENT, but don't see
those lines in the email I receive.

   There are no errors in Jenkins' log.


> If you look at the console log for any job, then right at the bottom, you
> can see what emails were sent. That might help.

   It says it's sending an email;  I just get the Jenkins default email.


   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.

   Is that not the case?  Do I have to *disable* the default email settings
(“E-mail Notification”) and only set up Email-Ext?

   But then, at the moment I would appear to have both set up, and I don't
get 2 emails (the global “Extended E-mail Notification/Override Global
Settings” *isn't* ticked, so it should be seeing my default email config.)

--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit

Reply | Threaded
Open this post in threaded view
|

Re: Can't get email-ext plugin to work

Neil Bird
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

Reply | Threaded
Open this post in threaded view
|

Re: Can't get email-ext plugin to work

Jan Seidel-2
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 <[hidden email]> 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
Reply | Threaded
Open this post in threaded view
|

Re: Can't get email-ext plugin to work

Neil Bird
Around about 04/04/12 10:44, Jan Seidel typed ...
> I have as example the following content in the global setup of email-
> ext:
> ------------- SNIP ------------------
> Changes since last build:
> $CHANGES

   Thanks;  I found the magic “show me the variables” button!

--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit