<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/05/2012 21:32, Mark Banner wrote:<br>
</div>
<blockquote cite="mid:4FA6DFD0.201@mozilla.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
What's different:<br>
<ul>
<li>New tbpl: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://tbpl.mozilla.org/?tree=Thunderbird-Trunk">https://tbpl.mozilla.org/?tree=Thunderbird-Trunk</a></li>
<ul>
<li>No tinderbox view anymore</li>
</ul>
<li>Nightly builds are going straight to the new aus server.
Only those with the update urls set to the new server will get
updates, so if you're on an old Daily build it may take two
updates to get to the latest build.</li>
</ul>
<p>What's new & broken:</p>
<ul>
<li>Pretty much the same as for the new try server, except that
the pending & running status is working fine.</li>
</ul>
</blockquote>
I forgot a couple of bits:<br>
<ul>
<li>We're not currently generating builds off of mozilla-central
pushes. This is <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=749108">bug
749108</a> and will be the highest priority to fix once we've
got the automation switch complete.</li>
<li>Using the self-serve API to create new builds off a revision
doesn't work (bug
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
752821), which means it can't be used as a work around to the
previous bug.</li>
<ul>
<li>However, you can use the '+' symbol for rebuild which will
still update the mozilla-central revision that a build is
based on (it'll keep the comm-central revision fixed).</li>
</ul>
</ul>
<p>Mark.<br>
</p>
<br>
</body>
</html>