<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
We've now moved the Try server automation fully over to the systems
that Firefox has been running on.<br>
<br>
For most of it, the experience will be the same - you push to
try-comm-central, and your builds come out in the same location in
try-builds. There's a few differences though, so here's the
highlights:<br>
<br>
What's different:<br>
<ul>
<li>To view the builds use: <a class="moz-txt-link-freetext"
href="https://tbpl.mozilla.org/?tree=Thunderbird-Try">https://tbpl.mozilla.org/?tree=Thunderbird-Try</a></li>
<ul>
<li>There is no tinderbox view any more.<br>
</li>
</ul>
<li>You will be required to use the try syntax when pushing (<a
class="moz-txt-link-freetext"
href="http://trychooser.pub.build.mozilla.org/">http://trychooser.pub.build.mozilla.org/</a>).
This is to help us not use all the builders when we don't need
to.</li>
<ul>
<li>The builders are dedicated try server builders, but are also
shared with the Firefox try server.</li>
</ul>
<li>The Mac builds are now being produced on OS X 10.7. They are
still using the 10.6 sdk and compatible with 10.5. This matches
the Firefox builders.<br>
</li>
</ul>
<br>
What's new:<br>
<ul>
<li>We now have unit tests running on debug builds</li>
<li>If you have level 1 access with an LDAP login, then you can
access the self-serve build api. This gives you:</li>
<ul>
<li>ability to request a rebuild of a specific build (click on
the build and then click the '+' icon in the middle of the
build info).</li>
<li>ability to cancel pending/running builds</li>
<li>get a list of all the running/pending builds with actions to
cancel/rebuild them (a link appears on the right when you
hover over the changesets/builds.</li>
</ul>
<li>We can now dynamically hide builds (those who know the sheriff
password for tinderbox can do this)</li>
<ul>
<li>You can see the list of hidden builds by going to Tree Info
-> Open tree admin panel<br>
</li>
</ul>
<li>Starring builds with the bug number will post a comment to the
bug.<br>
</li>
</ul>
<p>What's broken:<br>
</p>
<ul>
<li>The notification emails currently have the wrong links to the
builds in them (<a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=749151">bug
749151</a>)</li>
<li>Pending & Running builds aren't visible on tbpl (<a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=751066">bug
751066</a>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
)</li>
<li>Notification emails are not sent for failed builds, I suspect
this may be related to the same issue as the pending &
running builds<br>
</li>
<li>Some of the debug builds and tests are hidden (various bugs,
will be filing as we go forward)</li>
<li>We're still getting start of try build notification emails
from the old server - this will be dropped when we finish
switching the automation</li>
</ul>
<p>Mark<br>
</p>
</body>
</html>