Closed brianhw closed 6 years ago
@mulby As a potential vessel of institutional knowledge, do you have any memories as to why this might be an issue (and why we didn't change this sooner)? I fear I'm forgetting something basic.
I don't remember...
I think the original issues with upgrades was described in AN-4322. And I think we were able to start upgrading pip by changing the pipeline to "only run virtualenv venv
if we know an environment is not there already." So I think this should be fine.
Also created bug for this: DE-373.
Jenkins is running with ancient versions of pip and setuptools in its mkvirtualenv. This upgrades the versions of each that jobs are run with.