2

I'm using the Email-Ext plugin to send a results email at the end of my build in the post build stage of a declarative pipeline. In the body of the email I'm trying to insert some environment variables and some user defined environment variables.

The built in variables show up fine, however any user defined variables I define are just empty in the body of the email or don't work in the attachmentPattern field either:

My environment variables:

pipeline {
    agent any
    environment {
        buildFolder = "build_${BUILD_NUMBER}" 
        robotFolder = "build_${BUILD_NUMBER}/robotDemo" 
        serverName = "abc123"
        robotResults = "${buildFolder}/*.txt"
    }

The email-ext format I am using in my post{} build:

emailext attachLog: true, attachmentsPattern: 'build_${env.BUILD_NUMBER}/Robot_Results.txt', body: '<b>Job Name:</b> ${ENV, var="JOB_NAME"}<br><b>Build Number:</b> ${ENV, var="BUILD_NUMBER"}<br><br><b>Build URL:</b><br>${ENV, var="BUILD_URL"}<br><br><b>Log Files:<br><br><br><pre>${BUILD_LOG_EXCERPT, start="^====", end="^report.html"}</pre><pre>${ENV, var="serverName"}</pre>', mimeType: 'text/html', subject: 'ABS Results', to: 'richard.scott@sap.com'

For example: ${ENV, var="JOB_NAME"}, shows up fine. However ${ENV, var="serverName"} doesn't show at all.

I've tried variations such as...

${serverName}
${env.serverName}

...but they don't work either.

Any ideas how to use user defined environment variables like 'serverName' above in the email-ext plug-in?

Thanks & best regards, Richard.

RCS
  • 23
  • 1
  • 4
  • Did you find anything? I mean how this serverName can be used inside email body? – User Apr 28 '21 at 08:35
  • It worked ok once I used triple quotes: emailext body: ""' ${env.serverName} """ – RCS Apr 29 '21 at 09:21
  • 1
    I tried this way as well, but no luck so far. so could you please share your thoughts here https://stackoverflow.com/q/67330505/4306260 – User Apr 30 '21 at 08:19

1 Answers1

0

You’re using single quotes, but only double quotes allow variables to be interpolated.

I would suggest you to use a Groovy script for rendering the email contents.

You can either use the predefined Groovy script like this:

emailext body: '''${SCRIPT, template="groovy-html.template"}'''

Or add your own template like described in the documentation. I couldn't figure our if it's possible to load that template from the workspace, but you could try it with:

emailext body: '''${SCRIPT, template="$WORKSPACE/groovy-html.template"}'''

The syntax for getting values from the environment or parameters when interpolating is:

${env.MY_ENVVAR}
${param.MY_BUILDPARAM}

(env and param is ja Groovy map holding all the values)

And for all other variables:

${varName}
crash
  • 603
  • 4
  • 11
  • 1
    Your answer points towards a plausible solution. The referenced documentation is quite complex for such a small task. I'd give a +1 for the actual example of the script.template file. – jonni83 May 06 '21 at 18:51