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?