2d9d24d07d
We still have some Ubuntu Xenial servers, so cap the max usable pip and setuptools versions in their venvs like we already do for Bionic, in order to avoid broken installations. Switch our conditionals from release name comparisons to version numbers in order to more cleanly support ranges. Also make sure the borg run test is triggered by changes to the create-venv role. Change-Id: I5dd064c37786c47099bf2da66b907facb517c92a |
||
|---|---|---|
| .. | ||
| tasks | ||
| README.rst | ||
README.rst
Create a venv
You would think this role is unnecessary and roles could just install
a venv directly ... except sometimes pip/setuptools get out
of date on a platform and can't understand how to install compatible
things. For example the pip shipped on Bionic will upgrade itself to a
version that doesn't support Python 3.6 because it doesn't understand
the metadata tags the new version marks itself with. We've seen similar
problems with wheels. History has shown that whenever this problem
appears solved, another issue will appear. So for reasons like this, we
have this as a synchronization point for setting up venvs.
Role Variables