Confirm
3,990
edits
Changes
update notes
# rm desktop_unittest.py; ln firefox_ui_updates.py desktop_unittests.py
#* You have to hard-link since archiver [http://mxr.mozilla.org/build/source/tools/buildfarm/utils/archiver_client.py#175 does not allow symlinks on Windows]
# apply [https://bug1192309.bmoattachments.org/attachment.cgi?id=8647170|this patch]#* Just before calling [http://hg.mozilla.org/mozilla-central/file/default/testing/mozharness/scripts/firefox_ui_updates.py#l104 super()] create a new it modified the sys.argv values [1]# * You can either need to specify through ENABLE_BITS if to test all 6432-bit jobs or the 3264-bit jobs with this logic [2]builds
# after that you can push to try with this commit message (try: -b o -p android-x86 -u none -t none)
#* The try message should contain at least one platform that would be triggered on buildbot, otherwise, we want won't be able to use BuildApi since the revision won't exist unless there is at least one platform to schedule
# once you push to try, you will have to schedule a job with Mozilla CI tools
#* pip install -U mozci
#* export REVISION=your_try_revision_here
#* ''mozci-trigger --cancel-all try $REVISION'' (not yet implemented - use on TH meanwhile)the running Android x86 build#* mozci-See section below on how to trigger -b "Ubuntu VM 12.04 x64 try opt test mochitest-1" -r $REVISION --file http://who-cares.com#** Using --file is a necessary hack that avoids checking if there is an existing build [1] Specifying a sys.argv: 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(' ') [2]from mozharness.base.script import platform_nameENABLE_BITS='64'# Ignore that for Linux 32 the key is linux64 and Windows 64-bit is win32PLATFORM_FLAGS = { '32': { 'linux': '--cfg releng_infra_configs/linux.py ' + \ '--update-verify-config mozBeta-firefox-linux.cfg', 'linux64': '--help', 'win32': '--cfg releng_infra_configs/win32.py ' + \ '--update-verify-config mozBeta-firefox-win32.cfg', }, '64': { 'linux': '--help', 'linux64': '--cfg releng_infra_configs/linux64.py ' + \ '--update-verify-config mozBeta-firefox-linux64.cfg', 'macosx': '--cfg releng_infra_configs/macosx64.py ' + \ '--update-verify-config mozBeta-firefox-mac64.cfg' , 'win32': '--cfg releng_infra_configs/win64.py ' + \ '--update-verify-config mozBeta-firefox-win64.cfg' , },}tests
== 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 listtwo sets of commands.We can test on On a push we can either test the 64-bit platforms or the 32-bit ones.
* Ubuntu 64-bit, Windows 8 64-bit and Mac OS X
ENABLE_BITS=64
export REVISION=03abd4caa54e && \
mozci-trigger -b "Ubuntu VM 12.04 x64 try opt test mochitest-1,Rev5 MacOSX Yosemite 10.10 try opt test mochitest-1,Windows 8 64-bit try opt test mochitest-1" -r $REVISION --file http://dummy.com
* Ubuntu 32-bit and Windows 7 32-bit
ENABLE_BITS=32
export REVISION=20bbdfa06139 && \
mozci-trigger -b "Ubuntu VM 12.04 try opt test mochitest-1,Windows 7 32-bit try opt test mochitest-1" -r $REVISION --file http://dummy.com
NOTE: Using --file is a necessary hack that avoids checking if there is an existing build
== Using your own repositories ==
