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 20:51, 20 September 2022
, 20 September 2022move note about .mozconfig to prerequisite section
(add info on commit message example) |
(move note about .mozconfig to prerequisite section) |
||
| Line 218: | Line 218: | ||
== Operation Checklist == | == Operation Checklist == | ||
* Prerequisites | * 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. | |||
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) | ||
| Line 233: | Line 234: | ||
* Operational notes | * 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>. | ||