OpenH264 is a codec plugin allowing Firefox users to use WebRTC. We provide updates via Balrog.
The request comes from the media team. The latest bug is this one.
The last two updates happened because of changes on the Mac side (the M1 chip requiring eac arm support, macOS Monterey making notarization requirements more strict).
The openh264-plugin kind automates builds. We can update the revision we pull from the Cisco repo (to date we seem to pull from firefox-specific branches).
Ideally these builds Just Work, but since we don’t currently run these regularly, most likely there will be bustage.
We also have an openh264-signing kind; if we add-new-jobs these tasks, we should get signed builds.
However, we need to mac sign-and-notarize the mac binaries; as of 2022.06.16 we only gpg-detached-sign these. bug 1774669 to automate this; currently we only have the manual steps documented
Uploading to Cisco#
Currently we only allowlist ciscobinary.openh264.org as a valid domain to download binaries for balrog.
That step is manual: send an email or bugzilla needinfo.
Create the Balrog release#
- Create a new release and upload the new blob to Balrog:
on https://balrog.services.mozilla.com/releases click the “Add new release” button;
on the Create Release page, select “OpenH264” as the Product;
on the Create Release page, click “Upload Release” and select the file containing the new release blob;
verify that the new release blob has been uploaded and the “Release” name correctly identifies the release (eg. “OpenH264-18.104.22.168”);
on the Create Release page, click “Create Release” button in the lower right to create the release.
(It may be easier to download the previous-good blob to edit than to create the blob from scratch; it will look similar to OpenH264-22.214.171.124, except in json format.)
Create the Balrog rule#
- Create a new rule to test the release on the nightlytest channel:
on https://balrog.services.mozilla.com/rules click the “Add Rule” button
on the Create Rule page, set Product = “OpenH264”, Channel = “nightlytest” (or as needed), Mapping = the release you just created, Background Rate = 100 (or as needed), and set the Priority as needed, typically the lowest priority for the default rule.
on the Create Rule page, click “Create Rule” button in the lower right to create the rule.
See https://mozilla-balrog.readthedocs.io/en/latest/database.html for general guidance on rule matching.
OpenH264 updates are generally sent to all channels, though we can restrict by update channel (e.g.
esr* to only target esr users or nightlytest, the internal testing channel). This means users are given a new OpenH264 plugin based on their Firefox version. For instance: if we provide a new OpenH264 to 98.0 at the time 98.0b15 ships, then users with 98.0b1-b14 will also get this version. Make sure with the media team these betas are compatible! In the case it’s not, please remember Firefox doesn’t send which beta it’s on to Balrog. You have to filter out based on the version and the buildID (the buildID alone doesn’t work if a 97 dot release happens afterwards).
You can use the nightlytest channel to test changes before sending them to production. An OpenH264 request to balrog is like this one: https://aus5.mozilla.org/update/3/GMP/102.0/20180802174131/WINNT_x86_64-msvc-x64/en-US/nightlytest/default/default/default/update.xml