Build:TryServer: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 21: Line 21:
== Using a custom mozconfig ==
== Using a custom mozconfig ==


If you want to use setting other than those in the [http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2/linux/tryserver default mozconfigs ] (linux example).  Then you need to push to the $topsrcdir either:
If you want to use setting other than those in the [http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2/linux/tryserver default mozconfigs ] (linux example).  Then you need to push an '''extra file''' to the $topsrcdir either:


* .mozconfig-extra with settings to be applied to all mozconfigs
* '''.mozconfig-extra''' with settings to be applied to all mozconfigs
* .mozconfig-extra-$platform to apply changes only to that platform's mozconfig
* '''.mozconfig-extra-$platform''' to apply changes only to that platform's mozconfig


The options you enable/disable in your custom mozconfig are appended to the existing config after the default set.
The options you enable/disable in your custom mozconfig are appended to the existing config after the default set.


== What Gets Tried ==
== What Gets Tried ==

Revision as of 15:52, 19 May 2010

Try Server As Branch

The try server is an easy way to test a patch on all mozilla-central platforms without actually checking the patch into the core repository. You need a Mozilla hg account (level 1) to use push to try.

This new version of Try Server is called try-as-branch because it now works as a branch in the release automation configs in order to match the mozilla-central configs. With this setup we get many benefits in the try server namely debug builds, packaged unittests, and a way to keep tryserver in sync with mozilla-central as enhancements are made to it.

How to push to try

To submit a change to the try server:

  • For changes to mozilla-central or close enough (e.g. tracemonkey branch), you can hg push -f ssh://hg.mozilla.org/try/
    or
    hg push -f ssh://<username@host@>hg.mozilla.org/try/

To see the results:

If you're using Mercurial queues, the push -f command pushes any patches that are currently applied, and the Try server will build the result. (This is an awesome feature, not a bug!)

You don’t need to clone or pull from the try repo, and you probably don’t want to. You’d get every half-baked changeset anybody ever tested.

See Jorendorff's blog for more details.

Using a custom mozconfig

If you want to use setting other than those in the default mozconfigs (linux example). Then you need to push an extra file to the $topsrcdir either:

  • .mozconfig-extra with settings to be applied to all mozconfigs
  • .mozconfig-extra-$platform to apply changes only to that platform's mozconfig

The options you enable/disable in your custom mozconfig are appended to the existing config after the default set.

What Gets Tried

The Try server currently reports on the following trees:

A push to try kicks off these builders by default:

Builder If successful triggers
$platform tryserver build $platform tryserver opt test everythingelse, $platform tryserver opt test mochitests-{1-5}
$platform tryserver leak test build $platform tryserver debug test everythingelse, $platform tryserver debug test mochitests-{1-5}
Maemo try hg build
Talos runs for each successful build for a platform

Other Notes

  • Suggestions for the future can be made here

Other Mozilla Try Servers