Closed gyzpunk closed 6 years ago
withPythonEnv
was previously not playing nicely with environmental variables; however that has been remedied with version 2.0.0. I recommend upgrading to the new version, and seeing if your problems persist.
Closing due to inactivity
I'm facing the following issue when trying to use
withPythonEnv
in combination with ShiningPanda for a custom Python (miniconda3):returns:
Here is my pipeline step:
But, the following step is behaving well (which is roughly what the previous should do):
The environment variable
LD_LIBRARY_PATH
is properly configured in my Jenkins global configuration and contains a lib path withlibpython3.6m.so.1.0
in it.withPythonEnv
is behaving as it is flushing the whole env variables (or creating a new shell out of Jenkins ?) and then loosing all the variables customization available in Jenkins.