Closed
Bug 1461683
Opened 6 years ago
Closed 6 years ago
upgrade virtualenv + pip
Categories
(Release Engineering :: General, enhancement)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
(Whiteboard: [releng:q22018])
Attachments
(1 file, 1 obsolete file)
We're using an ancient version of both of these. This patch has been tested oun buildduty-tools, and worked fine. My intent is to pin a few canaries to my environment to start with, to make sure it works on various different machine types and virtualenvs. I've replaced "distribute" with "setuptools", and added the new "wheel" dependency. I also stopped passing "--distribute" (it's ignored), and added "--trusted-host" to workaround the fact that we're installing over HTTP (we should fix this, but probably as a follow-up).
Attachment #8975811 -
Flags: review?(aki)
Comment 1•6 years ago
|
||
Comment on attachment 8975811 [details] [diff] [review] upgrade pip + virtualenv Nice!
Attachment #8975811 -
Flags: review?(aki) → review+
Comment 2•6 years ago
|
||
Comment on attachment 8975811 [details] [diff] [review] upgrade pip + virtualenv I'm under the impression newer pip requires https. If that's the case, I think modifying the `servers.uniq.each do` line and user pip.conf to use https should work.
Assignee | ||
Comment 3•6 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #2) > Comment on attachment 8975811 [details] [diff] [review] > upgrade pip + virtualenv > > I'm under the impression newer pip requires https. If that's the case, I > think modifying the `servers.uniq.each do` line and user pip.conf to use > https should work. I think you can get around it with --trusted-host.
Comment 4•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Attachment #8975811 -
Attachment is obsolete: true
Comment 5•6 years ago
|
||
Comment on attachment 8976648 [details] Upgrade to latest versions of virtualenv, pip, setuptools, and wheel on python 2.7 installs. Aki Sasaki [:aki] has approved the revision. https://phabricator.services.mozilla.com/D1302
Attachment #8976648 -
Flags: review+
Pushed by bhearsum@mozilla.com: https://hg.mozilla.org/build/puppet/rev/e60e5ba1209f Upgrade to latest versions of virtualenv, pip, setuptools, and wheel on python 2.7 installs. r=aki
Assignee | ||
Comment 7•6 years ago
|
||
The upgrade for python 2.7 went largely OK. There were some issues where particular machines didn't puppetize correctly the first time (I'm pretty sure these are all due to bad dependencies in Puppet), but it looks like everything did fine on the second try. Because we didn't change anything of real note (eg: python or a first class dependency), I didn't restart all of the buildbot masters and signing servers. I did restart a few signing instances and one buildbot master to make sure they'll come up fine next time.
Assignee | ||
Comment 8•6 years ago
|
||
This is done! Python 3 was handled in bug 1458329.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•