I don't think it will. Email-ext is there for that purpose. On Thu, Apr 21, 2016, 04:00 Erik Vande Velde <[email protected]> wrote:
> Thanks! Now it works, but the email-ext needs a lot of configuration to > make it do what I want to, so i hope that one day the default mailer will > resolve variables too ... > > > On Thursday, April 21, 2016 at 11:41:22 AM UTC+2, slide wrote: > >> The default mailer does not do token replacement in any field. If you >> want that functionality, you need to use email-ext. >> >> On Thu, Apr 21, 2016 at 2:36 AM Erik Vande Velde <[email protected]> >> wrote: >> > (1) The release I'm running is 1.583 >>> (2) I'm using the regular mailer, not the extended one >>> (3) I copy pasted the name of the variable, I'm 100% sure it is correct >>> (4) I put an 'env' command in the job configuration (as our jenkins runs >>> on windows), and is showing my variable >>> So i'm sure the problem is that the mailer doesn't pick up my variable, >>> while it exists in the jenkins environment. >>> A question: when you look at your job's console output do you see >>> ${DAQ_MX_email_list} or the resolved variable value ? >>> >>> On Wednesday, April 20, 2016 at 3:51:28 PM UTC+2, >>> [email protected] wrote: >>> >>>> We use variables exactly as per your method (1), and it just works. >>>> Syntax is ${DAQ_MX_email_list}. >>>> >>>> You’re going to need to give us a bit more info about your >>>> configuration. >>>> >>>> What release of Jenkins are your running? Are you using the regular >>>> mailer, or the extended email plugin? >>>> >>>> Sorry to ask, but I assume that you have checked the spelling or the >>>> variable name. >>>> >>>> >>>> >>>> Can I suggest adding a build step that does an echo “$mail_list”? You >>>> need to work out whether the problem is that the variable is not set, or >>>> whether it is set, but the mailer is not picking it up. >>>> >>>> >>>> >>>> Hope that helps >>>> >>>> Matthew >>>> >>>> >>>> >>> *From:* [email protected] [mailto:[email protected]] >>>> *On Behalf Of *Erik Vande Velde >>>> >>> >>>> *Sent:* 20 April 2016 14:14 >>>> *To:* Jenkins Users >>>> *Cc:* Erik Vande [FGCB] Velde >>>> *Subject:* How can we use a variable for E-mail Notification >>>> Recipients field of a job ? >>>> >>> >>>> >>>> I tried the following: >>>> >>>> (1) define a global variable in Jenkins - Manage Jenkins - Configure >>>> system, and refer to it with ${mail_list} => the variable was not resolved >>>> >>>> (2) define properties in a local properties file, and access them from >>>> the EnvInject plugin => the variable is again unresolved >>>> >>>> According to >>>> http://stackoverflow.com/questions/21224481/how-to-set-environment-variable-so-that-it-can-be-used-in-jenkins >>>> we have to reference the variable with "$email_list" >>>> >>>> => none of "$email_list",$email_list and ${email_list} seem to work >>>> for me >>>> >>>> (3) I had a brief look at extended mail plugin documentation, and they >>>> don't talk about using a variable for the recipient either ... >>>> >>>> -- >>>> >>>> >>>> >>>> -- >>>> >>>> This e-mail and any attachments may contain confidential, copyright and >>>> or privileged material, and are for the use of the intended addressee only. >>>> If you are not the intended addressee or an authorised recipient of the >>>> addressee please notify us of receipt by returning the e-mail and do not >>>> use, copy, retain, distribute or disclose the information in or attached to >>>> the e-mail. >>>> Any opinions expressed within this e-mail are those of the individual >>>> and not necessarily of Diamond Light Source Ltd. >>>> Diamond Light Source Ltd. cannot guarantee that this e-mail or any >>>> attachments are free from viruses and we cannot accept liability for any >>>> damage which you may sustain as a result of software viruses which may be >>>> transmitted in or with the message. >>>> Diamond Light Source Limited (company no. 4375679). Registered in >>>> England and Wales with its registered office at Diamond House, Harwell >>>> Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United >>>> Kingdom >>>> >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/1ff54c70-7760-4cce-a719-69f2a23ddca6%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/1ff54c70-7760-4cce-a719-69f2a23ddca6%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/f3bad37c-0481-45f3-87c5-6d06b34c677b%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/f3bad37c-0481-45f3-87c5-6d06b34c677b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVduNoa8iuZxJZ2q1Q1bfmb-r8vSXDwKBkVdVZPr70t81A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
