What do you mean "environment variables or project parameters that were set by
someone"?

I understand what akshay_abd means because I have the same problem.

It seems to be impossible to use build parameters defined on build as tokens.

For example, on the same job where I use the email-ext plugin, I have defined PROJECT_BUILD_NAME as build parameter, but when I use $PROJECT_BUILD_NAME, it does not print the value has defined during build, instead it prints parameter name.
I've also tried to use ${ENV, PROJECT_BUILD_NAME}, ${ENV.PROJECT_BUILD_NAME} and $ENV.PROJECT_BUILD_NAME, but no one worked.

You should reference the parameter you defined (or the environment variable) with the following syntax:
${ENV,var="PARAMETER_NAME_UPPERCASE"}

For example, if you defined as parameter MYPAR you can use it into your message / subject of email-ext as:
${ENV,var="MYPAR"}

Why is it that we can't use a build parameter in the recipient field? I've tried similar combo's to those documented above by asalicetti

 This issue & its duplicate 5322 were both closed, while it was not clearly stated whether the issue was solved. 

In any case, I am trying the different alternatives proposed above and still, none of them work.

I have also tried several ways and nothing seems to work.  The duplicate may be closed since it was referring to documentation but I believe this issue needs to be re-opened unless someone can confirm it works with the current build.  

Still not solved, I want to use an Environment Variable as the recipient.

Environment variables can be referenced like this (at least for pipeline jobs):

${build.environment['PARAM_NAME']}

It works for me, at least in the email body when using SCRIPT (did not test with JELLY_SCRIPT).

It works for environment variables and job parameters which jenkins exposes as env variables.

It does not work for env variables set after the build started for example using env.PARAM="value".

I also confirmed that the suggested syntax does not work.

I hope this helps
Mor

Mor L in the body it works, but not in the recipient list.

Guillermo Martinez If you use pipeline to send the email - then I do not see the problem. If you do not use pipeline, well... I guess I can't help.

This is with the pipeline.  It is a problem with the recipient list in the pipeline.  I haven't tried it since my last post but I assume its in the same state.  Anywhere else your method works Guillermo Martinez, just not in the recipient list.

scott carlson I fail to see why you have problems with pipeline - since pipeline has env available to you - you don't need a special syntax.

So this would be like:

emailext body: 'A Test EMail', subject: 'Test', to: env.YOUR_PARAM

Am I missing something?

In all other instances in pipeline it works fine.. it is only with the "to:" section specifically there is an error.  every other instance in the body, subject, etc. it works fine.

For sanity I have tried 

• to: env.PARAM
• to: ${build.environment['PARAM']}
• to: "${env.PARAM}"
• to: "${build.environment['PARAM']}

none of them worked. 

If you are able could you try to use it in the "to:" section?

scott carlson

Not sure what is wrong with your setup - but it works. Tested with the following code (job has a single parameter called PARAM1 with value someone@somewhere.com):

node {
    echo env.PARAM1
    emailext body: "body",
             subject: "subject",
             to: env.PARAM1
}

output:

Started by user myuser
[Pipeline] node
Running on somenode in F:\somefolder
[Pipeline] {
[Pipeline] echo
someone@somewhere.com
[Pipeline] emailext
Sending email to: someone@somewhere.com
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS

It simply doesn't work as expected. Having this in the emailext body just doesn't work:

<p>Build #$BUILD_NUMBER ran on ${env.NODE_NAME} ${build.environment['NODE_NAME']} and terminated with $BUILD_STATUS.</p>

It prints to something like this in the sent email:

Build #54 ran on ${env.NODE_NAME} ${build.environment['NODE_NAME']} and terminated with Still Failing.

I've tried pretty much all combinations I've seen on the internet and the documentation. None of them work as expected - they will either print as empty or will print "as-is" without being replaced (like in the example above). 

Mor L's  example works, though.

not work for me too