Closed Bug 851371 Opened 9 years ago Closed 9 years ago

Change dm.catFile -> dm.pullFile

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jgriffin, Assigned: jgriffin)

References

Details

(Whiteboard: [mozbase])

Attachments

(1 file)

Mozharness uses a now-removed mozdevice method, catFile.  We should change this to pullFile instead.
Depends on: 848843
Whiteboard: [mozbase]
Attachment #725195 - Flags: review?(wlachance)
Assignee: nobody → jgriffin
Comment on attachment 725195 [details] [diff] [review]
Change catFile to pullFile,

lgtm
Attachment #725195 - Flags: review?(wlachance) → review+
I'll spin the other mozdevice fixes off into a separate bug.  The difficulty here is that mozharness depends on mozdevice, but the same mozharness version is used across branches, while the version of mozdevice that may be used in different branches varies. 

This isn't a problem in this case since pullFile has always existed, but I can imagine it causing us big headaches with some future API change.

One solution would be to have mozharness install the version of mozdevice it needs locally, rather than using the version that happens to be in the virtualenv created for whatever harness it's running.
Filed a follow-up as bug 851573.
This is in production.

* we could use a requirements file with specific versions, rather than a range; if this were checked into the tree that would allow us to ride the trains
* if we're going to be accessing mozdevice APIs rather than calling an executable, we need to make sure those APIs are supported until they're not used anymore.  I suggest deprecating them and waiting at least one full train cycle (up to 24 weeks) before removing functionality like this.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.