122
edits
Media/WebRTC/libwebrtc Update Process/automation plan: Difference between revisions
Jump to navigation
Jump to search
Media/WebRTC/libwebrtc Update Process/automation plan (view source)
Revision as of 17:28, 1 December 2022
, 1 December 2022slight reformat and add instructions to create a bug for fast-forward with example
(Adding Elm Reset Instructions) |
(slight reformat and add instructions to create a bug for fast-forward with example) |
||
| Line 226: | Line 226: | ||
== Operation Checklist == | == Operation Checklist == | ||
=== Prerequisites === | |||
Builds are done after vendoring in each commit. Having a <code>.mozconfig</code> file that enables cache (either sccache or ccache) will improve the performance of the scripts. | - Create a new bug for the fast-forward update. It should depend on the previous fast-forward bug. [https://bugzilla.mozilla.org/show_bug.cgi?id=1800920 Bug 1800920] is an example. | ||
- Builds are done after vendoring in each commit. Having a <code>.mozconfig</code> file that enables cache (either sccache or ccache) will improve the performance of the scripts. | |||
hg clone https://hg.mozilla.org/projects/elm | hg clone https://hg.mozilla.org/projects/elm | ||
(cd elm && ./mach bootstrap --application-choice=browser && ./mach build) | (cd elm && ./mach bootstrap --application-choice=browser && ./mach build) | ||
git clone https://github.com/mozilla/libwebrtc moz-libwebrtc | git clone https://github.com/mozilla/libwebrtc moz-libwebrtc | ||
On macOS, the python module <code>requests</code> should be installed. | - On macOS, the python module <code>requests</code> should be installed. | ||
pip install requests | pip install requests | ||
=== Update steps === | |||
# Start from the elm checkout | # Start from the elm checkout | ||
cd elm | cd elm | ||
| Line 244: | Line 246: | ||
bash dom/media/webrtc/third_party_build/loop-ff.sh | bash dom/media/webrtc/third_party_build/loop-ff.sh | ||
=== Operational notes === | |||
- Running <code>prep-repo.sh</code> with a fresh github clone of moz-libwebrtc will likely display instructions on how to add recent moz-central changes made in <code>third_party/libwebrtc</code> to the top of the patch stack in github. This is expected and necessary for successfully vendoring changes into <code>third_party/libwebrtc</code>. | - Running <code>prep-repo.sh</code> with a fresh github clone of moz-libwebrtc will likely display instructions on how to add recent moz-central changes made in <code>third_party/libwebrtc</code> to the top of the patch stack in github. This is expected and necessary for successfully vendoring changes into <code>third_party/libwebrtc</code>. | ||