I recently upgraded the EnvInject plugin from 1.33 to 1.85. Now, it doesn't work; i.e., the environment variables I set are not respected by later steps. For example, I choose "Inject environment variables to the build process" and set Properties Content to java.library.path=C:\something\something, but later on, when I call an Ant build step, this value is not used.
If I instead choose the build step "Execute Windows batch command", with the content: set ANT_OPTS=-Djava.library.path=C:\something\something cd C:\my\workspace ant my-job -Dmy-param1=value1 -Dmy-param2=value2 the job works as expected. So it seems that the environment variable that I set is somehow not being preserved in version 1.85. Has anyone else experienced this? It seems like such a basic failure that I feel like the problem must be on my end, that I must have missed something. When I downgrade the EnvInject plugin back to 1.33, the first scenario (with the Ant build step) works, so I feel pretty sure the issue is isolated to the EnvInject plugin. Thanks, -- Jerry -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
