Jenkins : Report results of intermediate [windows batch] build steps in email body

Question

As part of a Jenkins build process we run a couple Windows batch scripts and would like to report some information about these intermediate steps in the email that gets send

Answer 1

Environment variables set inside a build step do not propagate outside under the 'normal' circumstances. You can do the following:

• Install EnvInject Plugin
• Set environment variables and save them into a property file in the form VAR=VALUE
• In next build step import the file with EnvInject plugin (after installing the plugin you'll see 'Inject environment variables' among build step options). The variables will be available throughout the build.