Ben's Blog

This morning I landed bug 486567 – which cleaned up the try server code significantly. There’s still more to be done there, particularly running unittests on packaged builds once it’s production counterpart lands (bug 383136). Both of these things help us keep the Try Server in sync with the rest of the world – which has always been a problem.

Looking forward a little bit, I’m looking to land a patch that enables e-mail notification for try server builds and unit tests on Tuesday. With this patch, every try submission would result in 6 e-mails to the submitter: (1 per platform/build type combination). Here’s what they’ll look like:
Build:
Your Try Server build (try-1c170baeac1) was successfully completed on linux. It should be available for download at http://build.mozilla.org/tryserver-builds/bhearsum@mozilla.com-try-1c170baeac1

Visit http://hg.mozilla.org/MozillaTry to view the full logs.

Unit test:
Your Try Server unit test (try-1c170baeac1) completed with warnings on linux. It should be available for download at http://build.mozilla.org/tryserver-builds/bhearsum@mozilla.com-try-1c170baeac1

Summary of unittest results:
check: 2/0

Visit http://hg.mozilla.org/MozillaTry to view the full logs.

(The unittest e-mails will have the full results listed, of course).

E-mail notification has been an oft requested feature so I’m really excited that this will be landing soon.

During this time we will be landing two things:
* Test reporting to graphs.mozilla.org for codesighs and leak tests on mozilla-central (
bug 433710)
* Support for pushing try server builds to an hg.m.o repository (details later) (bug 448014)

No downtime is expected.

If there is any reason why we shouldn’t go ahead with this please e-mail release@mozilla.com

Not much else to say – bug 437143 (try servers need to support building from a mercurial repository with a patch) has been fixed. You can now submit patches against HG repositories with a patch.

Many thanks to Vlad, who did most of the work on this.

Not much else to say – bug 437143 (try servers need to support building from a mercurial repository with a patch) has been fixed. You can now submit patches against HG repositories with a patch.

Many thanks to Vlad, who did most of the work on this.

Once or twice a month a bug is filed on the try server. I see all of these go by and typically say something like “this would be cool, I don’t have time to do it”. Someone mentioned to me that they were going to blog about a specific try server to try and get some traction on it and I thought, “Why didn’t I think of that?”. So, the rest of this post is just a list of try server bugs that are relatively simple try server bugs that shouldn’t be too difficult to fix.

Bug 391364 – Tryserver should have the option of building specified platforms

Requires changes to: CGI script/UI, master.cfg/Buildbot steps

Bug 411735 – Client side form validation

Requires changes to: CGI script/UI

Bug 411735 – Support building from an alternate revision/branch/tag in a mercurial based try server build

Requires changes to: CGI script/UI, master.cfg/Buildbot steps

Bug 430942 – If bug # given, automatically add comment to bugzilla when try build finishes

Requires new Buildbot Status plugin

Bug 431375 – Try server needs to be able to handle non-Firefox builds

Requires changes to: CGI script/UI, master.cfg/Buildbot steps

Bug 431400 – Try server should support downloading bugzilla attachments as well as receiving uploaded patches

Requires changes to: CGI script/UI

I am happy to give guidance to and assist anyone who wants to work on any of these bugs. The CGI/UI can be found here: http://lxr.mozilla.org/mozilla/source/webtools/buildbot-try, the buildbot master.cfg is here: http://lxr.mozilla.org/mozilla/source/tools/buildbot-configs/tryserver/, and classes supporting it are here: http://mxr.mozilla.org/mozilla/source/tools/buildbotcustom/tryserver/.

On April 21, 2008 between 5am and 7am PDT the Try Server will be down for maintenance. For the curious, details of the work are in bug 428308.

The Mozilla2 and Mobile Buildbots will also be down for migration to a new host. Details of this work are in bug 429562.

If there’s any reason we can’t go ahead with this please e-mail release@mozilla.org.

On April 21, 2008 between 5am and 7am PDT the Try Server will be down for maintenance. For the curious, details of the work are in bug 428308. If there’s any reason we can’t go ahead with this please e-mail release@mozilla.org.

As of earlier today, the try server began uploading windows debugging symbols to a symbol server. For those of you interested in debugging your Windows try server builds you can follow the same instructions listed on devmo replacing http://symbols.mozilla.org/firefox with http://build.mozilla.org/tryserver-symbols. (For posterity, this information is also recorded on the try server wiki page. Any problems discovered should be filed (as always) in Webtools:Try Server.

There’s been some small but important updates to the Try Server the past week. Here’s a list!:

• One additional Windows slave and one additional Linux slave were added. This should reduce the length of time it takes to get your patches tested.
• configure.in changes can now be tested.
• The build timeouts were bumped up to an hour (of inactivity). This will allow builds that take a long time to link libxul (such as WPO optimizations) to build successfully.
• A Bugzilla Webtools::Try Server component has been created. Any future Try Server bugs should be filed there.

Johnath has gone to the trouble to make the try server look much nicer. I’ve been hoping someone would do this for awhile. It’s now got a nice favicon, sensible title, and better layout. Check it out here (ldap required).