See JENKINS-5580 for how this same problem was resolved for Batch Tasks plugin.. perhaps you can submit a patch based on that.

I am having mixed results with ver. 2.6:

An env var like `Major' or `MAJOR' declared as a build parameter always returns a value of `1', but an env var like `MAJOR_NO' returns the actual/correct value. I have another build parameter with an underscore and it works, and any other system env vars look good too.

Thank you,
Zach

This may also be related to JENKINS-7075.. I'm not sure if the vars provided by setenv plugin are among those not currently available to post-build actions.

Fwiw, this is the workaround I am using in order to generate text and then email it using the Extended Email plugin. Basically I prefix certain lines of the console log with a token, and then I use the Extended Email plugin's BUILD_LOG_REGEX feature to filter for lines that contain that token.

Let's say my build generates a logfile called my_logfile, which is what I want to include. What I do is cat out the file and prefix each line with the token "EMAIL:"

cat my_logfile | perl -lpe '$_=qq{EMAIL:\t $_}'

Then in "Default Content" field of the Extended Email plugin I can say:

${BUILD_LOG_REGEX, regex="EMAIL:\\t (.*)", substText="$1", showTruncatedLines=false}

And that results in sending an email that contains the content of my_logfile

Is this still an issue with the latest plugin and Jenkins?

This is still not working in mail-ext.

Since setenv is deprecated, have you tried EnvInject?

No, how would one do that ?

Install the EnvInject plugin and setup the injection of the environment variables, then see if the variables are available via the $ENV_VAR or ${ENV, var="ENV_VAR"} syntax.

This is not a defect in the email-ext plugin.