-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins ver. 1.642
Environment Injector Plugin 1.90
Setup with a build slave
If a file exists in slave home directory, e.g. /home/jenkinsslave/env.properties, then injecting environment variables will fail, if the Properties File has the same name.
Top level file exists:
...
+ cat env.properties
VERSION=123
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties file path 'env.properties'
[EnvInject] - Variables injected successfully.
...
/home/jenkinsslave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3/bin/mvn versions:set -DnewVersion=$VERSION
Top level file does not exist:
...
+ cat env.properties
VERSION=123
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties file path 'env.properties'
[EnvInject] - Variables injected successfully.
...
/home/jenkinsslave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3/bin/mvn versions:set -DnewVersion=123
- duplicates
-
JENKINS-23666 Change resolution order for the property files
-
- Open
-
Just tripped on this issue.
In my case it was caused because on the Prepare Environment I had a shell script that created a properties file.
It seems the default folder at that point is the Jenkins home folder.