Build:TryServer: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Using a custom mozconfig: values of $platform per catlee on irc)
Line 6: Line 6:
== How to push to try ==
== How to push to try ==
To submit a change to the try server:
To submit a change to the try server:
* For changes to mozilla-central or close enough (e.g. tracemonkey branch), you can <code>hg push -f ssh://hg.mozilla.org/try/</code> <br/>''or''<br/><code>hg push -f ssh://&lt;username@host@&gt;hg.mozilla.org/try/</code>
* For changes to mozilla-central or close enough (e.g. tracemonkey branch), you can <code>hg push -f ssh://hg.mozilla.org/try/</code> <br/>''or''<br/><code>hg push -f ssh://&lt;username@host@&gt;@hg.mozilla.org/try/</code>


To see the results:
To see the results:

Revision as of 20:09, 25 June 2010

Try Server

The try server is an easy way to test a patch without actually checking the patch into the core repository. Your code will go through the same tests as a mozilla-central push, and you'll be able to download builds if you wish.

To use try server, you need a Mozilla hg account (level 1 is sufficient).

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, you can push an extra file to the $topsrcdir:

  • mozconfig-extra with settings to be applied to all mozconfigs
  • mozconfig-extra-$platform to apply changes only to that platform's mozconfig, where $platform is one of linux, linux64, win32, macosx, macosx64

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

The default mozconfigs used for tryserver builds are available in Hg: http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/$platform/tryserver (linux example)

Disabling specific platforms for try push

You can put exit 1 in any mozconfig-extra-$platform in order to cause it to not compile. This is a temporary workaround while we get the web interface back up and with more granularity for selecting the build/test/perf runs desired for a particular try push.

Pending builds

You can find information about pending builds and server load at http://build.mozilla.org/builds/pending/try.html .

Other Notes

  • Suggestions for the future can be made here

Other Mozilla Try Servers