Open
Bug 1256975
Opened 8 years ago
Updated 9 months ago
VirtualenvMixin should provide a way to specify requirements via commandline/config
Categories
(Release Engineering :: Applications: MozharnessCore, enhancement, P5)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
NEW
People
(Reporter: ahal, Unassigned)
Details
Attachments
(4 files)
Currently various test scripts are hardcoding their requirements, e.g: https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/scripts/desktop_unittest.py#254 But it's not possible for a particular job or config file to specify a different set of requirements. Which means every job installs every requirement, whether it's needed or not. The commandline argument for this should be added to 'virtualenv_config_options': https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/base/python.py#45 It would be nice to have support for both requirements files, as well as just standard specificiers like <package-name>.
|
||
Updated•7 years ago
|
Priority: -- → P5
|
||
Updated•11 months ago
|
Severity: normal → N/A
Type: defect → enhancement
| Comment hidden (spam) |
| Comment hidden (spam) |
| Comment hidden (spam) |
| Comment hidden (spam) |
You need to log in
before you can comment on or make changes to this bug.
Description
•