Here is the ouput of the job running today with EnvInject 1.36
12:38:15 + cp /mnt/buildsjenkins/7.0_RC_Continuous-20/BuildFingerprint.txt .
12:38:15 [EnvInject] - Injecting environment variables from a build step.
12:38:15 [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
12:38:15 [EnvInject] - Variables injected successfully.
12:38:15 [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
12:38:15 [EnvInject] - Unset unresolved 'PATH' variable.
12:38:15 [EnvInject] - Unset unresolved 'NEWSCP' variable.
12:38:15 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
12:38:15 [EnvInject] - Unset unresolved 'TEMP' variable.

And the content of /mnt/buildsjenkins/7.0_RC_Continuous-20/BuildFingerprint.txt
[BuildInfo]
BuildId=2012-04-10_12-37-30
BuildNumber=20
DBBuildNumber=4775
BuildName=7.0_RC_Continuous-20
SymbolStoreUUID=92113861832b11e1b3bf00219b99e084
HGRev=c65e9f8e929175f8706a8a51bfecdb10da78503c
Branch=prerelease-7.0-RC

The config is the same that I already have attached.

As I said, the Master Jenkins is running on Windows and the slave on Linux, I don't know if that changes anything.

I can do more testing by creating a job that only injects the variables, if you want.

Thanks

Ok, I think I found it.
The injected file doesn't cause the error.
The problem is due to the internal EnvInject solving.
EnvInject gets Jenkins and build environment variables and then tries to merge them.
If a variable contains variable anymore, the variable is removed (or unset), it is not used by the Jenkins build).
Therefore, I suppose PATH, SRC_SHARED, NEWSCP, PYTHONPATH and TEMP are predefined environment variables and these variables can't resolve each other.
Could you check with the 'env' command?

They are indeed environment variables on the linux server. They are set in the .bash_profile file.

They are defined like this:
export DEVHOME=/usr/local/jenkins
export SRC_SHARED=${DEVHOME}/Projects/Shared
export NEWSCP=${DEVHOME}/Projects/DevTools/newscp

1. Python scripts
   export PYTHONPATH=${PYTHONPATH}:${DEVHOME}/Projects/DevTools/newscp
   export PATH=${PATH}:${DEVHOME}/Projects/DevTools/newscp:${DEVHOME}/Projects/DevTools/redhat

Does that help?
I'm not sure I understand what you mean by: these variables can't resolve each other.

I think these variables are not loaded by the Jenkins process.
Could you check if Jenkins process reads the .bash_profile file?

Jenkins expects to have all these variables resolved.
For example:
DEVHOME=/usr/local/jenkins
SRC_SHARED=${DEVHOME}/Projects/Shared
is OK because the SRC_SHARED variable can be resolved with DEVHOME value but only if DEVHOME is take into account (loaded by the Jenkins process).

Please check 'Manage Jenkins > System Information' and check if each variable can be resolved.

The variables were not defined in the Jenkins process, only in the .bash_profile.

Looks like the ssh command does not run the .bash_profile. I modified the launch script and they are now defined. I upgraded to the latest build of EnvInject (1.44) and it fixes the problem.

Thanks

I'm happy to read that

Just upgraded to version 1.60 and I got this error, which looks the same...

13:03:32 [EnvInject] - Injecting environment variables from a build step.
13:03:32 [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
13:03:32 [EnvInject] - Variables injected successfully.
13:03:32 [EnvInject] - Unset unresolved 'PATH' variable.
13:03:32 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.

Should be fixed from EnvInject 1.61

Is it fixed for your with the last version?
Can I set the issue to Resolved?

Validated fixed in 1.46