-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins 1.446, EnvInject 1.11
When using a property file with "Prepare an environment for the job" with a multi-configuration project, variables are not injected for each configuration.
By looking at the console output, the environment is indeed injected at the master job level (the one launching a job for each configuration). however, it doesn't help as it seems that the environment is re-created for each configuration job.
[JENKINS-12416] Environment is not injected for each configuration in a multi-configuration project
Gregory Boissinot
added a comment - Could you update your job configuration file in order I propose a fix in your configuration?
Gregory Boissinot
added a comment - Could you update your job configuration file in order I propose a fix in your configuration? 
Frederic Latour
added a comment - Not sure what you mean exactly. Frederic Latour
added a comment - I'm interested in having a possible fix but have a hard time guessing what you mean by asking if I could update my configuration job.
Mind to explain?
Frederic Latour
added a comment - I'm interested in having a possible fix but have a hard time guessing what you mean by asking if I could update my configuration job.
Mind to explain? Code changed in jenkins
User: Florence.Chabanois
Path:
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java
src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectVariableGetter.java
http://jenkins-ci.org/commit/envinject-plugin/2b8dcaa7f3e741746de8adbf3e6c0f204b1617f0
Log:
Fix JENKINS-12416
Gregory Boissinot
added a comment - It's a misunderstanding.
I wanted to say : Could you attach your job configuration file (config.xml) and not to update?
The issue should be fixed in the version 1.14.
Gregory Boissinot
added a comment - It's a misunderstanding.
I wanted to say : Could you attach your job configuration file (config.xml) and not to update?
The issue should be fixed in the version 1.14. Frederic Latour
added a comment - Thanks a lot Florence and gbois (or maybe this is the same person).
Frederic Latour
added a comment - Thanks a lot Florence and gbois (or maybe this is the same person). Gregory Boissinot
added a comment - It is the same person in this context (due to a git configuration issue)
Gregory Boissinot
added a comment - It is the same person in this context (due to a git configuration issue) 
As a workaround my idea was to inject environment using a Build Step. In that case however, I have no option for getting the properties file from the master which means I would have to maintain a file on each slave.