Closed Bug 1180739 Opened 9 years ago Closed 9 years ago

mach artifact install doesn't work with desktop build identifiers (macosx, win32, linux,linux64)

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(firefox42 affected)

RESOLVED FIXED
Tracking Status
firefox42 --- affected

People

(Reporter: Gijs, Unassigned, Mentored)

References

Details

(Whiteboard: [lang=python][good next bug])

(I've not actually tried the windows/linux flavours, but I image from the error message that they don't work either)
Nick, can you point me and/or other interested parties in the right direction here?
Flags: needinfo?(nalexander)
(In reply to :Gijs Kruitbosch from comment #1) > Nick, can you point me and/or other interested parties in the right > direction here? Yes! There are a few things needed here: 1) add an entry to the jobs listed here: https://dxr.mozilla.org/mozilla-central/source/python/mozbuild/mozbuild/artifacts.py#70 2) handle the TODO item about unpacking from different file types. You can see that I'm assuming a zip archive (aar files are just zips with certain contents), which doesn't apply to Desktop builds. 3) find a way to extract a version identifier (build ID? Task Cluster job id? Start with the latter) for the artifact, and then work it into the cached path in some way, so that you can handle build1/firefox-VERSION.tar.bz2 build2/firefox-VERSION.tar.bz2 ... Fennec doesn't have this issue, since the build ID is built into the artifact archive, like geckolibs-BUILDID1.aar geckolibs-BUILDID2.aar 4) you may need to parameterize the .so copying code, depending on the library types and destinations. At this point, consider extracting an abstract Job class that encapsulates these differences.
Mentor: nalexander
Flags: needinfo?(nalexander)
Whiteboard: [lang=python][good next bug]
This is done as of Bug 1236110 and Bug 1236111.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.