This works fine using Jenkins v1.520 and EnvInject v1.85.
Syntax is:
"${SCRIPTDIR}\job1-properties"
Be aware that:
1) If the file does not exist in the given path, EnvInject does not expand environment variables in the error message and will display something like "[EnvInject] - [ERROR] - The given properties file path '${SCRIPTDIR}\job1-properties' doesn't exist."
2) EnvInject seems to be sensible to casing of variable names. In your example, configuring the file path to "${scriptdir}\job1-properties" will result in an error (see 1)).
This works fine using Jenkins v1.520 and EnvInject v1.85.
Syntax is:
"${SCRIPTDIR}\job1-properties"
Be aware that:
1) If the file does not exist in the given path, EnvInject does not expand environment variables in the error message and will display something like "[EnvInject] - [ERROR] - The given properties file path '${SCRIPTDIR}\job1-properties' doesn't exist."
2) EnvInject seems to be sensible to casing of variable names. In your example, configuring the file path to "${scriptdir}\job1-properties" will result in an error (see 1)).