-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
WinXP
Not sure if this is a bug or a feature. I used to have global environment variables set via "Manage Jenkins->Configure System->Environment variables" and used these values as default values for my job. Per job I have use "paramterized builds" to overrule these global variables. After updating to more recent envinject plugin it seems like the logic has been flipped upside down. The global env vars overrule the parameter vars and I have not figured out how to enable the old logic?! Is it possible to make this behaviour configurable?
- relates to
-
JENKINS-14437 envinject fails to "really" set/override build parameters
-
- Reopened
-
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildVariableContributor.java
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper.java
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java
src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectScriptExecutor.java
src/main/java/org/jenkinsci/plugins/envinject/service/EnvironmentVariablesNodeLoader.java
http://jenkins-ci.org/commit/envinject-plugin/efb96d79b68d7f6d325bdd77cde3d33a6ae3c69c
Log:
Fix
JENKINS-16380