ReleaseEngineering/How To/Enable or Disable Updates on Central
From MozillaWiki
< ReleaseEngineering | How To
Occasionally a developer prepares to land a risky change to central, knowing that the next set of nightlies (or few sets) may be broken for updates.
When this happens we need to freeze updates to the latest known good version while QA and the developer decides to run some tests.
Note the magic rule ids below. These correspond to ids of rows in the "rules" table of Balrog. If we fix bug 1067402 we can pass more intelligable values here.
Disabling Updates
NOTE: You may not be able to run these scripts unless you have a linux laptop. See bug 1151633 for details and workarounds.
Fennec
# mozilla-central nightly cd /tmp rm -rf tools hg clone https://hg.mozilla.org/build/tools cd tools/scripts/updates scp cltbld@buildbot-master81.bb.releng.scl3.mozilla.com:/builds/buildbot/build_scheduler/master/BuildSlaves.py oauth.txt # Run with dry run first, sanity check the "Would've locked" lines. python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org -c oauth.txt -u ffxbld -r 4 -r 87 -n lock # Run without dry run to lock the updates python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org -c oauth.txt -u ffxbld -r 4 -r 87 lock
Firefox
cd /tmp rm -rf tools hg clone https://hg.mozilla.org/build/tools cd tools/scripts/updates scp cltbld@buildbot-master81.bb.releng.scl3.mozilla.com:/builds/buildbot/build_scheduler/master/BuildSlaves.py oauth.txt # Run with dry run first, sanity check the "Would've locked" lines. python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org -c oauth.txt -u ffxbld -r 3 -r 17 -n lock # Run without dry run to lock the updates python2.7 balrog-nightly-locker.py -a https://aus4-admin.mozilla.org -c oauth.txt -u ffxbld -r 3 -r 17 lock
Cleanup
# preferably with srm or equivalent srm oauth.txt
Enabling updates
Same as disabling, except change 'lock' to 'unlock'.