Releases/Firefox 13.0b6/BuildNotes: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 4: Line 4:
* no L10n milestone. I took no L10n changes
* no L10n milestone. I took no L10n changes
* change l10n-stage-sj.mozilla.org for l10n.mozilla.org in [https://wiki.mozilla.org/index.php?title=Release%3ARelease_Automation_on_Mercurial%3ADocumentation&action=historysubmit&diff=434857&oldid=429986 documentation]
* change l10n-stage-sj.mozilla.org for l10n.mozilla.org in [https://wiki.mozilla.org/index.php?title=Release%3ARelease_Automation_on_Mercurial%3ADocumentation&action=historysubmit&diff=434857&oldid=429986 documentation]
* I had to lock few extra darwin10 slaves since there were 4 attached but only 2 ssheable to start the mac builds (xulrunner was picked up first)
* I had to lock few extra darwin10 slaves since there were 4 attached but only 2 ssh-able to start the mac builds (xulrunner was picked up first)
* One of the mac repacks failed around Mon May 28 23:26:41 2012
* One of the mac repacks failed around Mon May 28 23:26:41 2012
  remoteFailed: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.
  remoteFailed: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.
* One of the mac repacls timed out on signing
* One of the mac repacks timed out on signing
** http://buildbot-master13.build.mozilla.org:8001/builders/release-mozilla-beta-macosx64_repack_4%2F6/builds/3/steps/run_script/logs/stdio
** http://buildbot-master13.build.mozilla.org:8001/builders/release-mozilla-beta-macosx64_repack_4%2F6/builds/3/steps/run_script/logs/stdio
** command timed out: 2400 seconds without output, attempting to kill
** command timed out: 2400 seconds without output, attempting to kill
Line 13: Line 13:
** Once the automation stops we can fix it by doing this:
** Once the automation stops we can fix it by doing this:
<pre>
<pre>
# do not run until all deliverables and logs are uplodaed
# do not run until all deliverables and logs are uploaded
cd /pub/mozilla.org/firefox/nightly
cd /pub/mozilla.org/firefox/nightly
rsync -av 13.0b6-candidates/ ../candidates/13.0b6-candidates/
rsync -av 13.0b6-candidates/ ../candidates/13.0b6-candidates/
Line 40: Line 40:
command: END (0.18s elapsed)
command: END (0.18s elapsed)
</pre>
</pre>
=Build Engineers=
=Build Engineers=
armenzg - Tracking bug: {{bug|744595}}
armenzg - Tracking bug: {{bug|744595}}
Line 57: Line 58:
| style="background:#efefef" | '''Changeset'''
| style="background:#efefef" | '''Changeset'''
|-  
|-  
| 1
| GECKO130_2012052815_RELBRANCH, FIREFOX_13_0b6_BUILD1 FIREFOX_13_0b6_RELEASE  
| GECKO130_2012052815_RELBRANCH, FIREFOX_13_0b6_BUILD1 FIREFOX_13_0b6_RELEASE  
| [http://hg.mozilla.org/releases/mozilla-beta/rev/046e86aee0c1 046e86aee0c1]
| [http://hg.mozilla.org/releases/mozilla-beta/rev/046e86aee0c1 046e86aee0c1]
Line 170: Line 172:


=== Reset reserved slaves ===
=== Reset reserved slaves ===
[cltbld@buildbot-master13 ~]$ echo 0 > /builds/buildbot/build1/master/reserved_slaves  
[cltbld@buildbot-master13 ~]$ echo 0 > /builds/buildbot/build1/master/reserved_slaves  


=== Check permissions / AV scan ===
=== Check permissions / AV scan ===
Line 182: Line 184:
rm -rf 13.0b6-candidates.old
rm -rf 13.0b6-candidates.old
</pre>
</pre>
</i>
* After retriggering it failed again
* XXX: the job has been re-triggered. Check that it went well.
<pre>
Traceback (most recent call last):
  File "/builds/slave/rel-m-beta-chk-prms/scripts/scripts/release/push-to-mirrors.py", line 176, in <module>
    buildNumber=buildNumber)
  File "/builds/slave/rel-m-beta-chk-prms/scripts/scripts/release/push-to-mirrors.py", line 84, in checkStagePermissions
    username=stageUsername, sshKey=stageSshKey)
  File "/builds/slave/rel-m-beta-chk-prms/scripts/scripts/release/../../lib/python/util/commands.py", line 57, in run_remote_cmd
    run_cmd(cmd_prefix + cmd, **kwargs)
  File "/builds/slave/rel-m-beta-chk-prms/scripts/scripts/release/../../lib/python/util/commands.py", line 42, in run_cmd
    return subprocess.check_call(cmd, **kwargs)
  File "/tools/python-2.5.1/lib/python2.5/subprocess.py", line 461, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ssh', '-l', 'ffxbld', '-i', '/home/cltbld/.ssh/ffxbld_dsa', 'stage.mozilla.org', 'test "0" = "$(find /pub/mozilla.org/firefox/nightly/13.0b6-candidates/build1/ -mindepth 1 -type d ! -perm 755 ! -path \'*/contrib*\' ! -path \'*/partner-repacks*\' | wc -l)"']' returned non-zero exit status 1
</pre>
XXX LOOK INTO THIS


=== Push to internal mirrors ===
=== Push to internal mirrors ===
Line 212: Line 228:
</pre>
</pre>
Remember to ssh to aus3-staging using your short LDAP name and then run <code>sudo su - ffxbld</code> once on.  If you intend to use screen, initiate your screen session while you are still yourself.<br />
Remember to ssh to aus3-staging using your short LDAP name and then run <code>sudo su - ffxbld</code> once on.  If you intend to use screen, initiate your screen session while you are still yourself.<br />
DONE TO HERE
 
<i>
==== Push to beta ====
==== Push to beta ====
Wait for "go" from release managers<br />
Wait for "go" from release managers<br />
For Firefox:
For Firefox:
* Publish (and record run time here): <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Beta_Release_.28Firefox_only.29|details]]''</small>
* Publish (and record run time here): <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Beta_Release_.28Firefox_only.29|details]]''</small>
** missed the time incantation on the pushsnip, but it was only a few minutes
* on completion, email r-d that VERSION updates are live on the beta channel
* on completion, email r-d that VERSION updates are live on the beta channel


DONE TO HERE
<i>
Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.
Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.
</i>
</i>
Confirmed users
4,293

edits

Navigation menu