Closed Bug 697492 Opened 13 years ago Closed 13 years ago

Should have a mozdevice API for interacting with remote devices

Categories

(Testing :: Mozbase, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wlach, Assigned: wlach)

References

Details

(Whiteboard: [mozbase])

We currently use two copies of the devicemanager API for interacting with remote devices in talos and mozilla-central automation. We should move this API into a mozbase module (I propose we call it mozdevice) and just have one copy of it that's usable by everything.
I'm going to take a stab at this.
Assignee: nobody → wlachance
Blocks: 697486
This is checked in here: https://github.com/wlach/mozbase/tree/mozdevice Probably no point in doing anything with this until we have an actual use case for this. Likely making talos use mozbase would be the first one (since we may as well replace its built-in devicemanager*.py with this if we're importing other components).
Is there any reason not to but it in mozilla/mozbase?
(In reply to Jeff Hammel [:jhammel] from comment #3) > Is there any reason not to but it in mozilla/mozbase? It's probably going to go out of date quickly, as devicemanagerSUT.py and devicemanagerADB.py change frequently as problems are found in production. We already have to sync these files between two places (m-c and talos), no point in adding a third.
Unassigning this from myself for now
Assignee: wlachance → nobody
Assignee: nobody → wlachance
Ok, it turns out that merging this helps Jeff a bit, so I just did so.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.