Confirm
3,990
edits
Changes
Added initial notes on how to test on the try server
If you specify specific actions (e.g. --run-tests) it will *only* executed that action and ignore the others.
= Test your changes on the Try server =
The Firefox UI tests are jobs that run when a release is running.
Unfortunately, you can't land changes on the various repositories and easily test your new changes until the next release happens.
This makes the development and testing cycle very difficult.
There is a hacky way to run these jobs on [https://treeherder.mozilla.org/ui/#/jobs?repo=try treeherder].
What we're going to do is hijack a job on buildbot to execute the firefox_ui_updates.py script and fake which arguments the script was called with.
You can use this patch or follow these steps:
# have a checkout of mozilla-central
# cd mozilla-entral/testing/mozharness/scripts
# rm desktop_unittest.py; ln firefox_ui_updates.py desktop_unittests.py
# Just before calling [http://hg.mozilla.org/mozilla-central/file/default/testing/mozharness/scripts/firefox_ui_updates.py#l104 super()] create a new sys.argv values:
command = 'scripts/scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg generic_releng_linux64.py --firefox-ui-branch mozilla-beta --update-verify-config mozBeta-firefox-linux64.cfg --tools-tag FIREFOX_40_0b6_RELEASE_RUNTIME --total-chunks 6 --this-chunk 1 --build-number 1'
sys.argv = command.split(' ')
# after that you can push to try with this commit message (TBD)
# once you push to try, you will have to schedule a job with Mozilla CI tools
#* pip install -U mozci
#* mozci-trigger -b "Ubuntu VM 12.04 x64 try opt test mochitest-1" -r 8d25a1dfde15 --file http://who-cares.com
#** Using --file is a necessary hack that avoids checking if there is an existing build
== Selecting the right platform and the right command ==
In order to set the right command on a job, you will have to grab it from these list.
You will have to adjust
* Ubuntu 64-bit
** buildername: Ubuntu VM 12.04 x64 mozilla-central opt test mochitest-1
** command:
scripts/scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg generic_releng_linux64.py --firefox-ui-branch mozilla-beta --update-verify-config mozBeta-firefox-linux64.cfg --tools-tag FIREFOX_40_0b6_RELEASE_RUNTIME --total-chunks 6 --this-chunk 1 --build-number 1
* Ubuntu 32-bit
** buildername: Ubuntu VM 12.04 mozilla-central opt test mochitest-1
** command:
scripts/scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg generic_releng_linux.py --firefox-ui-branch mozilla-beta --update-verify-config mozBeta-firefox-linux.cfg --tools-tag FIREFOX_40_0b6_RELEASE_RUNTIME --total-chunks 6 --this-chunk 1 --build-number 1
* Windows 7 32-bit
** buildername: Windows 7 32-bit mozilla-central opt test mochitest-1
** command:
scripts/scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg generic_releng_win32.py --firefox-ui-branch mozilla-beta --update-verify-config mozBeta-firefox-win32.cfg --tools-tag FIREFOX_40_0b6_RELEASE_RUNTIME --total-chunks 6 --this-chunk 1 --build-number 1
* Windows 8 64-bit
** buildername: Windows 8 64-bit mozilla-central opt test mochitest-1
** command:
scripts/scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg generic_releng_win6464.py --firefox-ui-branch mozilla-beta --update-verify-config mozBeta-firefox-win64.cfg --tools-tag FIREFOX_40_0b6_RELEASE_RUNTIME --total-chunks 6 --this-chunk 1 --build-number 1
* Mac OS X
** buildername: Rev5 MacOSX Yosemite 10.10 mozilla-central opt test mochitest-1
** command:
scripts/scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg generic_releng_macosx64.py --firefox-ui-branch mozilla-beta --update-verify-config mozBeta-firefox-mac64.cfg --tools-tag FIREFOX_40_0b6_RELEASE_RUNTIME --total-chunks 6 --this-chunk 1 --build-number 1
== Using your own repositories ==
You can append to the command this values:
* --firefox-ui-repo <git_repo>
* --firefox-ui-branch <git_branch>
* --tools-repo <hg_repo>
* --tools-tag <hg_tag>
== Re-triggering jobs ==
You don't need to push more changes to try if all you require is further changes to a Firefox UI repo or a tools repo.
You can simply push to your non gecko repos and re-trigger the job on Treeherder.
= Extra notes =
