Confirmed users
151
edits
(→Steps) |
(→Steps) |
||
| Line 12: | Line 12: | ||
If you've taken more than a few hours since the first clone, or want to be sure you are up to date, pull the latest and update your repo: | If you've taken more than a few hours since the first clone, or want to be sure you are up to date, pull the latest and update your repo: | ||
$ cd | $ cd src | ||
$ hg pull | $ hg pull | ||
$ hg update | $ hg update | ||
Now it's time to start adding the diffs: | |||
$ hg qimport ~/Documents/diffs/diff1 #(my patch) | |||
Repeat this step for all the diffs you want to add. | |||
$ hg qseries | |||
This should show the diffs you've added. | |||
$ hg qgoto diff1 | |||
Now you can begin the actual build process. | |||
[http://trychooser.pub.build.mozilla.org/ Try Chooser Syntax] is a tool that allows you to generate the try syntax you want. Try it out! | |||
For example, if I wanted to build only android native and android-xul, I would, after getting my try syntax, issue the following command: | |||
$ hg qnew -m "try: -b do -p android,android-xul -u all -t none" diff1 | |||
Actual syntax for the command is: | |||
$ hg qnew -m "try: <insert options here>" diff1 | |||
And then I push the lot to the server: | |||
$ hg push -f -rtip ssh://hg.mozilla.org/try | |||
Building, and if you opt to do so - running the tests- takes a fair bit of time but eventually your try build(s) are spit out here: | |||
https://tbpl.mozilla.org/ | |||
(click <font color="green">B</font> for relevant build and to go build directory at bottom) | |||
and here: | |||
https://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/ | |||
If the <font color="green">B</font> is of any other color, then the build has failed, or is still in progress. | |||
After pushing, I can remove the empty patch from my local repo: | |||
$ hg qpop | |||
$ hg qremove diff1 | |||
Hopefully this is enough to get you started, but more specifics on the topic can be found [https://wiki.mozilla.org/ReleaseEngineering/TryChooser/ here] | |||