forked from mirrors/gecko-dev
There are cases in CI where we're using the system Python, but we still want to create a virtualenv. For example, build jobs use the system Python packages, but Mozharness wants to have access to Mach packages. So, a virtualenv needs to be created (the `"common"` virtualenv), whose associated `python` binary is used to invoke Mozharness. So, just like for the `build` site, allow creating the `common` site even when the "native package source" is the system Python. Since `mach_virtualenv_requirements.txt` already depends on `common_virtualenv_requirements.txt`, this restriction should not cause validation breakage. Differential Revision: https://phabricator.services.mozilla.com/D140255 |
||
|---|---|---|
| .. | ||
| index.rst | ||