project-config/jenkins/scripts/run-tox-with-neutron-lib-master.sh
Armando Migliaccio ba4d707fcf Add pep8 to the script used by the periodic-with-neutron-lib job
This will help assess whether changes to the lib's hacking
incubating factory will break consumer projects.

Change-Id: I9bb173071abcbc5078a3fd728c41c34bf1b83ca2
2017-03-07 07:58:20 -08:00

40 lines
1.0 KiB
Bash
Executable File

#!/bin/bash -xe
# inspired from sister script run-tox-with-oslo-master.sh
venv=$1
if [[ -z "$venv" ]]; then
echo "Usage: $?"
echo
echo "VENV: The tox environment to run (eg 'py35')"
exit 1
fi
script_path=/usr/local/jenkins/slave_scripts
sed -i "s/neutron-lib.*/-e git+https:\/\/git.openstack.org\/openstack\/neutron-lib.git#egg=neutron-lib/g" requirements.txt
sed -i "s/neutron-lib.*/-e git+https:\/\/git.openstack.org\/openstack\/neutron-lib.git#egg=neutron-lib/g" upper-constraints.txt
cat << EOF >> tox.ini
[testenv:${venv}-neutron-lib-master]
setenv = VIRTUAL_ENV={envdir}
passenv = TRACE_FAILONLY GENERATE_HASHES http_proxy HTTP_PROXY https_proxy HTTPS_PROXY no_proxy NO_PROXY
usedevelop = True
deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
whitelist_externals = sh
commands =
{toxinidir}/tools/ostestr_compat_shim.sh {posargs}
EOF
set +e
$script_path/run-tox.sh pep8
pep8_code=$?
$script_path/run-tox.sh $venv-neutron-lib-master
venv_code=$?
set -e
exit_code=$(( $pep8_code || $venv_code ))
exit $exit_code