changeset 7303:f5b5749113aa stable

make-release: use a fresh virtualenv for building the release A user-provided virtualenv could contain extra packages or different versions, which may mask problems inside Kallithea.
author Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
date Sun, 18 Mar 2018 21:08:52 +0100
parents 1a3af9e025e2
children 92fd0b7ff4d9
files scripts/make-release
diffstat 1 files changed, 16 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/scripts/make-release	Sun Mar 18 20:52:26 2018 +0100
+++ b/scripts/make-release	Sun Mar 18 21:08:52 2018 +0100
@@ -2,6 +2,22 @@
 set -e
 set -x
 
+cleanup()
+{
+  echo "Removing venv $venv"
+  rm  -rf "$venv"
+}
+
+echo "Checking that you are NOT inside a virtualenv"
+[ -z "$VIRTUAL_ENV" ]
+
+venv=$(mktemp -d --tmpdir kallithea-release-XXXXX)
+trap cleanup EXIT
+
+echo "Setting up a fresh virtualenv in $venv"
+virtualenv -p python2 "$venv"
+. "$venv/bin/activate"
+
 echo "Install/verify tools needed for building and uploading stuff"
 pip install --upgrade -e .
 pip install --upgrade Sphinx Sphinx-PyPI-upload