Closed Bug 1111835 Opened 10 years ago Closed 3 years ago

Separate mozharness' virtualenv from the scripts' virtualenv

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: [easier-mozharness]) 

Currently, mozharness creates a virtualenv for the script is going to run for, however, this can be conflicting with other bugs like bug 928457.

I'm thinking that we should create an action called create-mozharness-virtualenv and that way we can separate the dependencies.

What do people believe?

I assume we will also be able to remove mozinfo, mozprocess and mozprocess from the repository and start using newer versions of it straight from releng's pypi.

I think I can get contributors to work on this if we all agree.
Whiteboard: [easier-mozharness]
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.