canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Build:TryServer: Difference between revisions
m
no edit summary
m (moved Build:TryServerAsBranch to Build:TryServer: request) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
# | = 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 [http://www.mozilla.org/hacking/committer/ Mozilla hg account] ([http://www.mozilla.org/hacking/commit-access-policy/ level 1] is sufficient). | |||
== How to push to try == | |||
To choose your tests: | |||
* ''In your commit message'', include a [[Build:TryChooser]] piece. | |||
To submit your changes 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://<username@host>@hg.mozilla.org/try/</code><br/>''or''<br/><code>hg push -f ssh://hg.mozilla.org/try/ -e 'ssh -l <username@host></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]. | |||
* Compare Talos perf numbers using Pike's [http://github.com/Pike/talos-node talos-node] or mconnor's [http://perf.snarkfest.net/compare-talos/ compare-talos]. | |||
* Download your completed builds from [http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/?C=M;O=D firefox/tryserver-builds on ftp.m.o]. | |||
If you're using [https://developer.mozilla.org/en/Mercurial_Queues 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. | |||
== How to get a talos run == | |||
* Wait until the platforms you are interested in have completed their 'build' jobs | |||
* Look on #build for a release engineer to trigger it for you | |||
* Provide them your "email-changeset" identifier from the tinderbox-builds on ftp rather than just your changeset - if you want all talos suites that's all you need to provide otherwise you may specify particular suites from the [http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla-tests/config.py#l19 available suites] | |||
* They will request your talos suites and that's it! | |||
== 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, android, maemo4, maemo5-gtk, maemo5-qt | |||
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/ http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/]$platform/tryserver ([http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/linux/tryserver linux example]) | |||
==Selecting specific platforms for try push== | |||
See [[Build:TryChooser]] for details on how to customize your try push in your hg commit comments. | |||
== Using a different mobile-browser repository == | |||
To use a different mobile-browser repository for the mobile builds, include extra files in your push in the $topsrcdir: | |||
*'''mobile-repo''' with a path (relative to http://hg.mozilla.org/) to the repository (e.g., "users/jford_mozilla.com/mobile-browser") | |||
*'''mobile-rev''' with a revision in that repository (e.g., "default") | |||
For more details, see [http://blog.johnford.info/mobile-on-the-new-try-server/ Mobile on the new try server] | |||
== Server Status == | |||
* Try server load can be seen at http://build.mozilla.org/builds/pending/try.html | |||
* Pending builds by revision are at http://build.mozilla.org/builds/pending.html | |||
* In-progress builds by revision are are http://build.mozilla.org/builds/running.html | |||
== Other Notes == | |||
* Finished builds will be deleted after '''14 days'''. | |||
* Try repo is reset '''occasionally''', and you may not be able to use TBPL to see your test results after it has been reset. | |||
* If you have any problems please [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Release%20Engineering&status_whiteboard=tryserver file a bug] | |||
* 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 | |||
* 1.9.2 try is coming soon ([https://bugzilla.mozilla.org/show_bug.cgi?id=563822 bug 563822]) | |||