2

I am quite new with configuring Jenkins or Python but I have to set up a unitary test in Jenkins. My program is in Python, but only works on Python 2.6 whereas the Jenkins version I should be using is 2.7, so I'm trying to set up Jenkins to set some environment variables so that it prepares launching the accurate Python for that specific test (it is part of a greater project that will successfully run several other tests that work well).

The idea I had was to set in the command to execute several environment variables like PATH, LD_LIBRARY_PATH and PYTHONPATH such as following in the "Execute shell" command line interpreter:

PYTHONPATH=/path/to/python2.6/lib:$PYTHONPATH
PATH=/path/to/python2.6/bin:$PATH
LD_LIBRARY_PATH=/path/to/python2.6/lib:$LD_LIBRARY_PATH

... however, it was still calling the wrong version of Python. Therefore, I forced these variables to:

PYTHONPATH=/path/to/python2.6/lib
PATH=/path/to/python2.6/bin
LD_LIBRARY_PATH=/path/to/python2.6/lib

... and I still get errors because the old version of Python is called instead, even if it should not appear in the PATH ... It appears Jenkins will remember the location of the old libraries however and will try loading them first.

How would I correctly set the environment in a "subproject" in Jenkins so that I can call a different version of Python?

Thank you and best regards,

~Stéphane

Improve this question

3 Answers 3

Reset to default
4

If you want your program to run with a specific version of the python interpreter, you indicate it in the shebang

#!/usr/bin/python2.6
#your code here
Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

I used your solution, and it works after debugging my code, so I cannot tell if it's helping or not; in the doubt I'd say yes. I didn't test yet if it's absolutely necessary, though.
1

What i did in my Jenkins shell script using a specific python version was something like this when calling my unit test:

python3 src/test/unit_test.py

I was using it to use Python 3.X but it should work with 2.6 as well using:

python2.6 src/test/unit_test.py
Improve this answer

1 Comment

Thank you for your answer, it helped me debugging my code... there was an error in it, causing the Python environment to go amok.
0

Stupid me... I was indeed doing things correctly, I just had a part of my code that was overriding the PYTHONPATH value, so the solution I had found previously was good. FYI, I modified my shebang, if it's of any help to anyone ;)

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.