1213772 - openh264 builds need to support uploading in brave new S3 world

Status: RESOLVED WORKSFORME

(Release Engineering :: Release Requests, defect)

Description

[Nick Thomas [:nthomas] (UTC+12)]

Doesn't truly block bug 1213721, we can manually work around.

testing/mozharness/scripts/openh264_build.py makes a call to self.rsync_upload_directory(), which will upload to ~ffxbld/openh264 by default.
This won't be available after we transition to S3 hosting. It's either post_upload or re-invent the process (direct to S3 bucket for Cisco to pick up?)

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Callek, what did you end up doing for v1.5 ?

Comment 2

[Justin Wood (:Callek)]

(In reply to Nick Thomas [:nthomas] from comment #1)
> Callek, what did you end up doing for v1.5 ?

for 1.5[.x] it used the rsync to stage.m.o, (home dir) I manually scp'd and moved some stuff around during this since we don't have the logic for *all* the things (e.g. android x86 and android arm).

We still need to figure out an s3-aware solution.

Comment 3

[Justin Wood (:Callek)]

current @ https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/scripts/openh264_build.py#227

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

We could just push these to a bucket which Cisco can GET from ? With a signed manifest ftw.

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

Callek, I think we did a openh264 in the last year, how did we handle uploads ?

Comment 6

[Justin Wood (:Callek)]

I manually scp'd them to a local system. Future plan is roughly a Taskcluster upload to a private/ bucket.

https://bugzilla.mozilla.org/show_bug.cgi?id=1286533#c6 has my latest work.

Comment 7

[Firefox Bug Husbandry Bot]

Bulk change of QA Contact to :jlund, per https://bugzilla.mozilla.org/show_bug.cgi?id=1428483

Comment 8

[Nick Thomas [:nthomas] (UTC+12)]

This is superceded by the work dminor did in bug 1513000 to build on taskcluster, and the resulting files are artifacts there.