Build:TryServer: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| 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 an '''extra file''' 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: | ||
| Line 27: | Line 26: | ||
* '''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 | 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 | ||
== Other Notes == | == Other Notes == | ||
| Line 33: | Line 32: | ||
* Try repo is reset '''occasionally''', and you may not be able to use TBPL to see your test results after it has been reset. | * 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] | * 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. | * 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. | ||
| Line 40: | Line 37: | ||
== Other Mozilla Try Servers == | == Other Mozilla Try Servers == | ||
* [https://wiki.mozilla.org/Thunderbird/Infrastructure/TryServer Thunderbird Try Server] for the comm-central repository | * [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]) | * 1.9.2 try is coming soon ([https://bugzilla.mozilla.org/show_bug.cgi?id=563822 bug 563822]) | ||
Revision as of 08:17, 13 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/
orhg push -f ssh://<username@host@>hg.mozilla.org/try/
To see the results:
- You'll get an email from each builder with results.
- Look for your changeset on the Try Tinderbox or Try TBPL.
- Compare Talos perf numbers using Pike's talos-node.
- Download your completed builds from firefox/tryserver-builds on ftp.m.o.
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. The default mozconfigs used for tryserver builds are available in Hg: http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/$platform/tryserver
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 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 here
Other Mozilla Try Servers
- Thunderbird Try Server for the comm-central repository
- 1.9.2 try is coming soon (bug 563822)