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 message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to