Open Bug 1256975 Opened 7 years ago Updated 6 years ago

VirtualenvMixin should provide a way to specify requirements via commandline/config


(Release Engineering :: Applications: MozharnessCore, defect, P5)



(Not tracked)


(Reporter: ahal, Unassigned)


Currently various test scripts are hardcoding their requirements, e.g:

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':

It would be nice to have support for both requirements files, as well as just standard specificiers like <package-name>.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.