venv/bin/activate does nothing more than tweak the right environmental paths.
You can do it yourself by adding at the beginning, assuming that env.WORKSPACEthis is the directory of your project:
env.PATH="${env.WORKSPACE}/venv/bin:/usr/bin:${env.PATH}"
, virtualenved python, , :
stage 'Test'
sh "${env.WORKSPACE}/venv/bin/python34 manage.py test --keepdb'
pip
sh "${env.WORKSPACE}/venv/bin/pip install -r requirements.txt"