Bug 1459077 - Install known working pip and virtualenv; r=ted
authorGregory Szorc <gps@mozilla.com>
Fri, 04 May 2018 13:10:50 -0700
changeset 818125 b5a639d810b82ae1885db83b253198f73bfcdbd4
parent 818124 8468d03b8e517eaf03a5bc4d6ae15832331b6317
child 818126 9db70a54f47cc819736da8b6772ba8f17a8585cb
push id116246
push userbmo:tom@mozilla.com
push dateFri, 13 Jul 2018 20:48:08 +0000
Bug 1459077 - Install known working pip and virtualenv; r=ted Previously, we installed the latest version of pip and virtualenv. This commit pins the pip and virtualenv version so we install known working versions (pip 10 breaks the image build for some reason). MozReview-Commit-ID: hOAMencdcr
--- a/taskcluster/docker/recipes/ubuntu1604-test-system-setup.sh
+++ b/taskcluster/docker/recipes/ubuntu1604-test-system-setup.sh
@@ -89,19 +89,18 @@ apt-get update
 export DEBIAN_FRONTEND=noninteractive
 apt-get install -y -f "${apt_packages[@]}"
 dpkg-reconfigure locales
 . /setup/common.sh
 . /setup/install-mercurial.sh
-pip install --upgrade 'pip<10.0'
-pip install virtualenv
+pip install pip==9.0.3
+pip install virtualenv==15.2.0
 . /setup/install-node.sh
 # Install custom-built Debian packages.  These come from a set of repositories
 # packaged in tarballs on tooltool to make them replicable.  Because they have
 # inter-dependenices, we install all repositories first, then perform the
 # installation.
 cp /etc/apt/sources.list sources.list.orig