MozillaWiki

Releases/Firefox 3.6.14/BuildNotes: Difference between revisions

Page Discussion

Releases/Firefox 3.6.14/BuildNotes (view source)

Revision as of 16:07, 2 March 2011

10,435 bytes added ,  2 March 2011
m
→‎Final Verification
 
(46 intermediate revisions by 5 users not shown)
Line 18: Line 18:
| FIREFOX_3_6_14_BUILD2
| FIREFOX_3_6_14_BUILD2
| [http://hg.mozilla.org/releases/mozilla-1.9.2/rev/77abb6fcd2b7 releases/mozilla-1.9.2/77abb6fcd2b7]
| [http://hg.mozilla.org/releases/mozilla-1.9.2/rev/77abb6fcd2b7 releases/mozilla-1.9.2/77abb6fcd2b7]
|-
| 3
| FIREFOX_3_6_14_BUILD3
| [http://hg.mozilla.org/releases/mozilla-1.9.2/rev/a73120a6aa93 releases/mozilla-1.9.2/a73120a6aa93]
|}
|}
= Notifications =
* We have to notify AV vendors once the signed bits are on candidates directory (for email address and template example, see {{bug|568884#c15}} )
* We have to give mirrors as much notice as possible before pushing to mirrors. This has been 24-72 hours, but has been up to a week in advance.  (for email address and template example, see {{bug|633657}} )
* We have to notify infra-all@ before "go to build" and before we ship. The more advance notice the better.
* We have to notify metrics once we release


= Bugs hit =
= Bugs hit =
Line 25: Line 35:
* <strike>{{bug|628795}} - en-US.xpi uploaded to the wrong place during 1.9.1/1.9.2 releases</strike>
* <strike>{{bug|628795}} - en-US.xpi uploaded to the wrong place during 1.9.1/1.9.2 releases</strike>
* <strike>{{bug|616512}} - Linux repacks will always fail to upload if run before win32 build finishes</strike>
* <strike>{{bug|616512}} - Linux repacks will always fail to upload if run before win32 build finishes</strike>
* {{bug|633961}} - pre push check fails
* <strike>{{bug|633961}} - pre push check fails</strike>
* [got backed out] {{bug|632399}} ctors steps
* [got backed out] {{bug|632399}} ctors steps
* <strike>{{bug|632412}} - signing regression for win32-EUBallot</strike>
* <strike>{{bug|632412}} - signing regression for win32-EUBallot</strike>
Line 39: Line 49:
* {{bug|629256}} - Fix snippets for some locales
* {{bug|629256}} - Fix snippets for some locales
* macosx_repack_2/6 died with SIGUSR1
* macosx_repack_2/6 died with SIGUSR1
** TODO check if it needs filing


=Build data=
=Build data=
Line 80: Line 89:
| w32-ix-slave23 ('''slow IX''')
| w32-ix-slave23 ('''slow IX''')
| 5 hrs, 11 mins, 35 secs
| 5 hrs, 11 mins, 35 secs
|-
| rowspan="3" | 3
| Linux
| 20110218124314
| moz2-linux-slave23
|
|-
| Mac
| 20110218124600
| bm-xserve16
|
|-
| Windows
| 20110218125750
| w32-ix-slave23 ('''slow IX''')
|
|}
|}


Line 192: Line 217:


Then continued by uploading as it would normally be done.
Then continued by uploading as it would normally be done.
=== Notify AV vendors ===
* Notify vendors using instructions in {{bug|568884#c15}}


=== L10n Verify ===
=== L10n Verify ===
Line 240: Line 268:
  rm -rf
  rm -rf
  20110126-Firefox-3.5.17-3.6.14-MU-bug629256fix/Firefox/3.5*/Darwin*/*/{kn,ml,te}
  20110126-Firefox-3.5.17-3.6.14-MU-bug629256fix/Firefox/3.5*/Darwin*/*/{kn,ml,te}
=== Email mirrors about release day date ===
They need to know 24-48 hours ahead of time.
<pre>
On $DATE1 or $DATE2, we plan to "push to
mirrors" for the Firefox '''$3_6_VERSION''' and Firefox '''$3_5_VERSION''' security releases.
If you believe this will cause any problems, or there are other releases
scheduled for those dates on mirrors, please let us know at
'''$RELEASE_MAILING_LIST'''.
Thanks
'''$NAME'''
</pre>


== Going live day! ==
== Going live day! ==
Line 249: Line 292:


=== Push to Mirrors ===
=== Push to Mirrors ===
'''DONE TO HERE'''
Skipping; doing a build 2.
 
<i>
Go to the "push to mirros" builder and add these two values:
* '''Revision to build''' FIREFOX_3_6_14_RELEASE
* '''Property 1 name''': release_config: mozilla/release-firefox-mozilla-1.9.2.py


=== Final Verification ===
=== Final Verification ===
Once mirror uptake has reached 50 or 60% this builder can be started with 'Force Build' from the Buildbot waterfal
Skipping; doing a build 2.
</i>


=== Push release channel snippets ===
=== Push release channel snippets ===
Please use the <tt>20110126-Firefox-3.6.14-bug629256fix</tt> directory when pushing to the release channel for 3.6.x -> 3.6.14 updates, for {{bug|629256}}. We drop updates for a few locales which have strings that make the updater crash. [[User:NThomas|NThomas]] 23:52, 26 January 2011 (PST)
Skipping; doing a build 2.


=== Push 3.0.19 -> 3.6.13 MU snippets ===
<i>Please use the <tt>20110126-Firefox-3.6.14-bug629256fix</tt> directory when pushing to the release channel for 3.6.x -> 3.6.14 updates, for {{bug|629256}}. We drop updates for a few locales which have strings that make the updater crash. [[User:NThomas|NThomas]] 23:52, 26 January 2011 (PST)</i>


=== Push EU Ballot build ===
=== Redirect EU Ballot build and add to bouncer ===
* Filed {{bug|632052}} to change download redirect
Skipping; doing a build 2.
* On bouncer we add "Firefox-3.6.14-EUballot" product under "Mirrors->Products->Add new product"
* Once added, we add a new mirror location:
/firefox/releases/3.6.14/win32-EUballot/:lang/Firefox%20Setup%203.6.14.exe
<i>
* Check with Tomcat to see if he has filed the website bug
</i>


=== Release ===
=== Release ===
Skipping; doing a build 2.


=== XULRunner Signing ===
=== XULRunner Signing ===
Skipping; doing a build 2.


=== Push XULRunner to mirrors ===
=== Push XULRunner to mirrors ===
Skipping; doing a build 2.


=== Update XULRunner entries on wiki ===
=== Update XULRunner entries on wiki ===
 
Skipping; doing a build 2.


=Build 2=
=Build 2=
Line 409: Line 443:
  cd /home/ftp/pub/mozilla.org/firefox/nightly/3.6.14-candidates/build2/
  cd /home/ftp/pub/mozilla.org/firefox/nightly/3.6.14-candidates/build2/
  mv win32-EUBallot win32-EUballot
  mv win32-EUBallot win32-EUballot
=== Notify AV vendors ===
* Notify vendors using instructions in {{bug|568884#c15}}


=== L10n Verify ===
=== L10n Verify ===
Line 482: Line 519:


Nothing to be done since nthomas landed some fixes in [https://bugzilla.mozilla.org/show_bug.cgi?id=629256#c10 bug 629256]
Nothing to be done since nthomas landed some fixes in [https://bugzilla.mozilla.org/show_bug.cgi?id=629256#c10 bug 629256]
=== Email mirrors about release day date ===
They need to know 24-48 hours ahead of time.
<pre>
On $DATE1 or $DATE2, we plan to "push to
mirrors" for the Firefox '''$3_6_VERSION''' and Firefox '''$3_5_VERSION''' security releases.
If you believe this will cause any problems, or there are other releases
scheduled for those dates on mirrors, please let us know at
'''$RELEASE_MAILING_LIST'''.
Thanks
'''$NAME'''
</pre>


== Going live day! ==
== Going live day! ==
Line 490: Line 542:
* '''Property 1 name''': release_config: mozilla/release-firefox-mozilla-1.9.2.py
* '''Property 1 name''': release_config: mozilla/release-firefox-mozilla-1.9.2.py


* <font color='red'>currently running: start 14:24PDT; ETA: 30mins</font>
* It failed the first time because of permission issues. {{bug|633961}}
* I triggered it a second time


DONE TO HERE
Skipping; doing a build 3.
<i>


=== Push to Mirrors ===
=== Push to Mirrors ===
Go to the "push to mirros" builder and add these two values:
Skipping; doing a build 3.
* '''Revision to build''' FIREFOX_3_6_14_RELEASE
 
* '''Property 1 name''': release_config: mozilla/release-firefox-mozilla-1.9.2.py
=== Final Verification ===
Skipping; doing a build 3.
 
=== Push release channel snippets ===
Skipping; doing a build 3.
 
=== Push EU Ballot build ===
Skipping; doing a build 3.
 
=== Release ===
Skipping; doing a build 3.
 
=== XULRunner Signing ===
Skipping; doing a build 3.
 
=== Push XULRunner to mirrors ===
Skipping; doing a build 3.
 
=== Update XULRunner entries on wiki ===
Skipping; doing a build 3.
 
=Build 3=
 
'''NOTE: We might not send this build to the users but build#2. This will be decided on Tuesday'''
 
* Clobbered with "Any master/any release/any builder"
* tagged with FIREFOX_3_6_14_BUILD3 and FIREFOX_3_6_14_RELEASE
** buildbot-configs on '''production'''
** buildbotcustom on '''production-0.8'''
** compare-locales & tools
* [http://hg.mozilla.org/build/buildbot-configs/rev/517992f6aa54 landed build2 changes]
* updated /tools/buildbotcustom/buildbotcustom, /builds/buildbot/configs, and /builds/buildbot/builder_master/tools to latest
* Left tree open, 0.8.0 automation doesn't require that it closes
* kicked off automation with:
 
PYTHONPATH=/builds/buildbot/builder_master:/builds/buildbot/builder_master/tools/lib/python python /builds/buildbot/builder_master/tools/buildbot-helpers/release_sanity.py -u armenzg -V 3.6.14 --branch mozilla-1.9.2 --build-number 3 -c release-firefox-mozilla-1.9.2.py --dryrun localhost:9010
 
=== Tag ===
No problems.
 
=== Version bump ===
Not needed as it is build3.
 
=== Update Bouncer ===
Not needed as it is build3.
 
=== Source / XULRunner Source ===
No problems.
 
=== XULRunner Build ===
No problems.
 
=== Build ===
No problems.
 
=== Start autosigning ===
If you are expecting to sign during your workday you can start [https://intranet.mozilla.org/Build:CombinedSigning auto signing] to take care of the deliverables as they are uploaded to FTP.
 
=== L10n Repack ===
No problems.
 
* repack 5/6 failed due to checkout timeout on slow slave
** re-triggered
 
=== Partner Repack ===
No problems.
 
=== Unittests ===
All three platforms fails with these:
39509 ERROR TEST-UNEXPECTED-FAIL | /tests/content/html/content/test/test_bug481335.xhtml | Should be visited now - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)"
39510 ERROR TEST-UNEXPECTED-FAIL | /tests/content/html/content/test/test_bug481335.xhtml | Should still be visited after setting pathname to its existing value - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)"
 
Notified LegNeato.
 
=== Signing ===
Followed [https://intranet.mozilla.org/Build:CombinedSigning CombinedSigning doc].
 
=== Notify AV vendors ===
* Notify vendors using instructions in {{bug|568884#c15}}
 
=== L10n Verify ===
I don't even see the point of this builder.
It's always red (expected) and the output does not tell you if there is anything wrong with it.
 
=== Updates ===
 
==== 3.6* -> 3.6.13 ====
===== Generation =====
We landed a fix to avoid this from happening but I forgot to reconfigure.
 
cd /builds/slave/rel-192-updates/
find build/temp/firefox/3.6.13-3.6.14/ftp/firefox/nightly/3.6.14-candidates/build3 -type f -exec chmod 644 {} \;
find build/temp/firefox/3.6.13-3.6.14/ftp/firefox/nightly/3.6.14-candidates/build3 -type d -exec chmod 755 {} \;
cd /builds/slave/rel-192-updates/build/temp/firefox/3.6.13-3.6.14/ftp/firefox/nightly/3.6.14-candidates/build3
rsync -av -e 'ssh -oIdentityFile=~/.ssh/ffxbld_dsa' --exclude=*complete.mar update ffxbld@stage-old.mozilla.org:/pub/mozilla.org/firefox/nightly/3.6.14-candidates/build3/
cd /builds/slave/rel-192-updates/build/temp/firefox/3.6.13-3.6.14
rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' aus2.test/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20110219-Firefox-3.6.14-test
cd /builds/slave/rel-192-updates/build
bash -c 'ssh -l cltbld -i ~/.ssh/cltbld_dsa aus2-staging.mozilla.org ~/bin/backupsnip 20110219-Firefox-3.6.14-test'
bash -c 'ssh -l cltbld -i ~/.ssh/cltbld_dsa aus2-staging.mozilla.org ~/bin/pushsnip 20110219-Firefox-3.6.14-test'
cd /builds/slave/rel-192-updates/build/temp/firefox/3.6.13-3.6.14
rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' aus2/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/20110219-Firefox-3.6.14
rsync -av -e 'ssh -oIdentityFile=~/.ssh/cltbld_dsa' aus2.beta/ cltbld@aus2-staging.mozilla.org:/opt/aus2/snippets/staging/2011019-Firefox-3.6.14-beta
bash /builds/slave/rel-192-updates/tools/release/compare-channel-snippets.sh aus2 release aus2.test releasetest
 
===== Update Verify =====
Same as with update verify for build2. 'mk' and 'te' failed for mac.
 
See {{bug|629256}} for more details.
 
=== Socorro product data updates ===
Already done for '''build 1'''
 
== Going to beta day!! ==
Do this in the morning before the rel-driver gives you the GO.
#From a build slave you can reach aus2-staging
#cltbld@aus2-staging.mozilla.org
cd /opt/aus2/snippets/staging/
~/bin/backupsnip 20110219-Firefox-3.6.14-beta # takes more than 45mins
 
To make backupsnip to work we had to re-enable updates ({{bug|636218}}):
#on aus2-staging and phx
cd /opt/aus2/incoming/3/Firefox/
chmod 700 -v 3.6*
 
=== Push to Beta Channel ===
#From a build slave you can reach aus2-staging
#cltbld@aus2-staging.mozilla.org
#This takes now a lot of time because of PHX datacenter
cd /opt/aus2/snippets/staging/
~/bin/pushsnip 20110208-Firefox-3.6.14-beta
 
=== Email mirrors about release day date ===
They need to know 24-48 hours ahead of time.
 
<pre>
On $DATE1 or $DATE2, we plan to "push to
mirrors" for the Firefox '''$3_6_VERSION''' and Firefox '''$3_5_VERSION''' security releases.
 
If you believe this will cause any problems, or there are other releases
scheduled for those dates on mirrors, please let us know at
'''$RELEASE_MAILING_LIST'''.
 
Thanks
'''$NAME'''
</pre>
 
== Going live day! ==
 
=== Final checks before push & virus scan ===
I trigger the builders last week and it all went well.
 
I trigger it once more manually to re-verify it.
clamdscan /mnt/netapp/stage/archive.mozilla.org/pub/firefox/nightly/3.6.14-candidates/build3/
/mnt/netapp/stage/archive.mozilla.org/pub/firefox/nightly/3.6.14-candidates/build3: OK
----------- SCAN SUMMARY -----------
Infected files: 0
Time: 5466.948 sec (91 m 6 s)
 
=== Backup release snippets ===
Do this in the morning ahead of time before the "push snippets to release".
#From a build slave you can reach aus2-staging
#cltbld@aus2-staging.mozilla.org
cd /opt/aus2/snippets/staging/
~/bin/backupsnip 20110219-Firefox-3.6.14
 
=== Push to Mirrors and modify exclude file ===
After some re-tagging and reconfigures for getting some changes that had landed on default we manage to trigger this builder and succeed to completion.
http://hg.mozilla.org/build/buildbotcustom/rev/03084b14ff4b
 
Push to community mirrors:
# cltbld@stage
vim -n /pub/mozilla.org/zz/rsyncd-mozilla-current.exclude
# replace 3.6.13 with 3.6.14


=== Final Verification ===
=== Final Verification ===
Once mirror uptake has reached 50 or 60% this builder can be started with 'Force Build' from the Buildbot waterfal
Triggered automatically.
</i>


=== Push release channel snippets ===
=== Push release channel snippets ===
The backupsnip was done earlier in the [[Releases/Firefox_3.6.14/BuildNotes#Backup_release_snippets backup release snippets]] section.
#From a build slave you can reach aus2-staging
#cltbld@aus2-staging.mozilla.org
cd /opt/aus2/snippets/staging/
~/bin/pushsnip 20110219-Firefox-3.6.14


=== Push 3.0.19 -> 3.6.13 MU snippets ===
=== Redirect EU Ballot build and add bouncer entry ===
Reopened {{bug|632052}} for IT to fix it when the snippets are live
 
NOTE: I think there is a bug that got fixed recently that adds the bouncer entry for the EUballot builds automatically. I can't find it right now.


=== Push EU Ballot build ===
* Filed {{bug|632052}} to change download redirect
* Filed {{bug|632052}} to change download redirect
* On bouncer we add "Firefox-3.6.14-EUballot" product under "Mirrors->Products->Add new product"
* On bouncer we add "Firefox-3.6.14-EUballot" product under "Mirrors->Products->Add new product"
* Once added, we add a new mirror location:
* Once added, we add a new mirror location:
  /firefox/releases/3.6.14/win32-EUballot/:lang/Firefox%20Setup%203.6.14.exe
  /firefox/releases/3.6.14/win32-EUballot/:lang/Firefox%20Setup%203.6.14.exe
<i>
* Check with Tomcat to see if he has filed the website bug
</i>


=== Release ===
=== Release ===
Update symlinks
#ffxbld@stage
cd /home/ftp/pub/firefox/releases
rm latest-3.6 && ln -s 3.6.14 latest-3.6
Sent the following mail to metrics@mozilla.com:
Firefox,firefox,firefox,3.6.13,3.6
Firefox,firefox,firefox,3.6.14pre,3.6


=== XULRunner Signing ===
=== XULRunner Signing ===
Create ~/signXR1.9.2.14.bash file with chmod +x and this content:
<pre>
#!/bin/bash
set -x
set -e
PRODUCT=xulrunner
VERSION=1.9.2.14
BUILD=3
TAG=FIREFOX_3_6_14_RELEASE
REPO="releases/mozilla-1.9.2"
EMAIL=armenzg@mozilla.com
KEYDIR=d:/2010-keys
cd ~/hg-tools
hg pull
hg up -r ${TAG}
mkdir -p ~/signing-work/${PRODUCT}-${VERSION}
cd ~/signing-work/${PRODUCT}-${VERSION}
cp ~/hg-tools/release/signing/* .
make setup PRODUCT=${PRODUCT} VERSION=${VERSION} \
  BUILD=${BUILD} REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1
rsync -av -e "ssh -i /home/cltsign/.ssh/xrbld_dsa" \
  --exclude=*.txt --exclude=*-symbols.zip \
  xrbld@stage.mozilla.org:/home/ftp/pub/${PRODUCT}/nightly/${VERSION}-candidates/build${BUILD}/ \
unsigned-build${BUILD}
rsync -av --exclude=unsigned unsigned-build${BUILD}/ \
signed-build${BUILD}/
rsync -av unsigned-build${BUILD}/unsigned/ \
signed-build${BUILD}/
make checksum-files create-sigs stage verify-sigs \
  PRODUCT=${PRODUCT} VERSION=${VERSION} BUILD=${BUILD} \
  REPO=${REPO} EMAIL=${EMAIL} KEYDIR=${KEYDIR} USE_NEW=1
rmdir signed-build${BUILD}/contrib{,-localized}
rsync -av -e "ssh -i /home/cltsign/.ssh/xrbld_dsa" \
  signed-build${BUILD}/ \
  xrbld@stage.mozilla.org:/home/ftp/pub/${PRODUCT}/nightly/${VERSION}-candidates/build${BUILD}/
</pre>


=== Push XULRunner to mirrors ===
=== Push XULRunner to mirrors ===
# xrbld@stage
rsync -av --exclude=*.txt --exclude=*unsigned*  --exclude=*-symbols.zip \
  /pub/mozilla.org/xulrunner/nightly/1.9.2.14-candidates/build3/ \
  /pub/mozilla.org/xulrunner/releases/1.9.2.14/
Edited cltbld@stage:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude and added
- xulrunner/releases/1.9.2.13


=== Update XULRunner entries on wiki ===
=== Update XULRunner entries on wiki ===
Updated the links in these two wiki pages for the version change:
* [https://developer.mozilla.org/En/XULRunner_1.9.2_Release_Notes Release Notes]
* [https://developer.mozilla.org/En/Gecko_SDK Gecko_SDK]
Armenzg
Confirmed users
3,990

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/284339...288022"