Build:TryServer: Difference between revisions

(Redirected page to ReleaseEngineering/TryServer)
 
(45 intermediate revisions by 14 users not shown)
Line 1: Line 1:
= Try Server =
#REDIRECT [[ReleaseEngineering/TryServer]]
== 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 <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:
* You'll get an email from each builder with results.
* Look for your changeset on the [http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTry Try Tinderbox] or [http://tests.themasta.com/tinderboxpushlog/?tree=MozillaTry Try TBPL].
* Download your completed builds from [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/ /tryserver-builds].
 
If you're using Mercurial queues, the <code>push -f</code> 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 <code>try</code> repo, and you probably don’t want to. You’d get every half-baked changeset anybody ever tested.
 
See [http://blog.mozilla.com/jorendorff/2008/08/18/push-to-try/ Jorendorff's blog] for more details.
 
== 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:
 
* .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:
 
* [http://hg.mozilla.org/mozilla-central/ mozilla-central].
 
A push to try kicks off these builders by default:
{| border="1" width="100%"
|+
|width="50%"|'''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 ==
* Finished builds will be deleted after '''14 days'''.
* If you have any problems please send mail to [mailto:release@mozilla.org release@mozilla.org]
* The default mozconfigs used for tryserver builds are available in Hg: http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2/$platform/tryserver
* Uploading an alternate mozconfig appends to the default mozconfigs.
* Windows builds have symbols uploaded to http://build.mozilla.org/tryserver-symbols. Windbg and the Visual Studio debugger may use them to help debug crashing try server builds. Instructions for setting this up can be found here: http://developer.mozilla.org/en/docs/Using_the_Mozilla_symbol_server. Make sure you use the aforementioned URL instead of http://symbols.mozilla.org/firefox.
 
* Suggestions for the future can be made [[Build:TryServer:Suggestions|here]]
 
== Other Mozilla Try Servers ==
 
* [https://wiki.mozilla.org/Thunderbird/Infrastructure/TryServer Thunderbird Try Server] for the comm-central repository

Latest revision as of 23:01, 21 September 2010