Re: How can we use a variable for E-mail Notification Recipients field of a job ?

I don't think it will. Email-ext is there for that purpose. On Thu, Apr 21, 2016, 04:00 Erik Vande Velde 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 >

Re: How can we use a variable for E-mail Notification Recipients field of a job ?

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

Re: How can we use a variable for E-mail Notification Recipients field of a job ?

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 wrote: > (1) The release I'm running is 1.583 > (2) I'm using the regular mailer, not the

Re: How can we use a variable for E-mail Notification Recipients field of a job ?

(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

RE: How can we use a variable for E-mail Notification Recipients field of a job ?

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,

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