ReleaseEngineering/How To/Generate partial updates: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 12: Line 12:
For the purposes of this doc we'll say the update will be between $OLDV and $NEWV build$BUILD.
For the purposes of this doc we'll say the update will be between $OLDV and $NEWV build$BUILD.


= Config files =  
= Create config files =  
== Patcher config ==
== Patcher config ==
To get setup
To get setup
Line 135: Line 135:


Announce to r-d so QA can test/include in testing.
Announce to r-d so QA can test/include in testing.
= Update Verify =
Do our full old + update == new checks.
On each platform that needs testing
* stop buildbot slave
* in a terminal (SSH is OK for linux & mac)
# windows
cd /e/builds/slave
# else
cd /builds/slave
# all platforms
mkdir bugXXXXXX; cd $_
hg clone http://hg.mozilla.org/build/tools scripts
hg -R scripts update -C -r FIREFOX_13_0_1_RELEASE_RUNTIME
cd scripts/release/updates/
# ZZZZZZ is the attachment number for the verify config
wget -O- https://bugzilla.mozilla.org/attachment.cgi?id=ZZZZZZ | patch -p3
# mac
bash verify.sh -c mozRelease-firefox-mac64-XXXXXX.cfg 2>&1 |tee uv.log; echo $?
# win32
bash verify.sh -c mozRelease-firefox-win32-XXXXXX.cfg 2>&1 |tee uv.log; echo $?
Verify exit code is 0, reboot slave to get back in service.
Confirmed users
4,293

edits

Navigation menu