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