ReleaseEngineering/ThunderbirdTryServer

Basic Use

The Thunderbird try server works in exactly the same way to the Firefox try server with a few minor differences. The automation is based on the same hardware and tools, so there should be few differences.

The Thunderbird try server is primarily for building Thunderbird. Whilst building other comm-central apps may work, this is not supported - builds and tests may fail etc.

Must Read

Please read the Firefox Try server page to get familiar with the basic workings of try server.

Please also use the TryChooser whenever possible to limit jobs and save builder time.

Differences

These are the differences for the Thunderbird try server:

• Patches should be pushed to ssh://hg.mozilla.org/try-comm-central
• Results go to the try-comm-central on treeherder
• Finished builds live on http://ftp.mozilla.org/pub/mozilla.org/thunderbird/try-builds/{your_email_changeset}

Tips and Tricks

• Pushing a try build with try-comm-central will always pick the latest m-c changeset.

Pushing mozilla-central patches

There's two steps to this process.

1. Edit client.py-args: remove the hgtool option, add --apply-patches
   • Example patch here
   • Do this as a separate item in your mq and you can use whenever you want
   • Note: hgtool option removal is because I'm not convinced if applying a patch affects the hg share or not
2. Take your mozilla-central patch and name it something like: mozilla-<anything>.patch
3. hg add your patch
4. Then hg commit your changes, or use hg qnew for a new item on your patch queue
5. Push your patches to try-comm-central

The client.py code will automatically apply your patch when the code is checked out. Any apply failures will cause the builds to be aborted.

Pushing ldap/chatzilla/venkman/DOM Inspector patches

The mozilla build system also supports modifying code from other hg.mozilla.org code repositories for testing on the try server. The approach for this is basically the same as in the Pushing mozilla-central patches section, except the patch file name has to be ldap-<anything>.patch, chatzilla-<anything>.patch, venkman-<anything>.patch or inspector-<anything>.patch depending on what patch you want to test.

Known issues

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);