I am seeing very odd behaviour after using the EnvInject plugin. I have created a job and all it does is print it's workspace path. Somehow the workspace is not as expected and it actually uses another job's workspace instead! What is going on? I notice that the <jobName>\builds\<build_id>\injectedEnvVars.txt file contains the incorrect workspace path.
- Is there a bug in the EnvInject plugin? shanz
