== How to push to try ==
=== Gecko 15-17 note ===
Try has switched to Pymake, so it won't normally work with Gecko 15-17 Win32 builds. To make Try work for those builds, add [https://gist.github.com/3582912 this patch] to your queue.
=== Running a subset of builds/test/talos available to Try===
You must use [[Build:TryChooser]] to choose which builds, tests, and talos you would like run on your push to try. Make sure you place the try chooser text in your ''topmost commit''. The [http://trychooser.pub.build.mozilla.org/ TryChooser] web page can help you build a commit message for custom requests, so can the [https://github.com/pbiggar/trychooser mercurial extension]
If you want to apply the same mozconfig changes to multiple platforms, you can edit <tt>build/mozconfig.common.override</tt> instead. This file is included at the end of each of the in-tree mozconfig files.
(Android mozconfigs are in mobile/android/config/mozconfigs or mobile/xul/config/mozconfigs.)
Note:
* TryServer purpose is to tell what will happen on Tinderbox, not to check every possible build option/configuration.
** Any non-standard feature is implicitly unsupported. You may try them, but don't complain if they break.
=== Old crufty way ===
For revisions prior to around Oct 4, 2011, you'll be using the default buildbot-configs based mozconfigs, and will need to add some extra files to your push.
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, linux-android, 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/try ([http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/linux/try linux example])
== Using older GCC ==
Linux and Linux64 build bots are using GCC 4.5 for Try builds. But some branches will fail to build or run tests with this version of GCC because of the libstdc++ dependency it adds. Such branches are those where [https://bugzilla.mozilla.org/show_bug.cgi?id=643690 bug 643690] hasn't landed. If you want to push such a branch to Try, you need to add the following to '''mozconfig-extra-linux''' and/or '''mozconfig-extra-linux64''' in the top directory:
CC=/tools/gcc-4.3.3/installed/bin/gcc
CXX=/tools/gcc-4.3.3/installed/bin/g++
== How to get non-PGO coverage ==
A lot of the following is out of date, see:
https://wiki.mozilla.org/ReleaseEngineering/TryChooser#What_if_I_want_PGO_for_my_build
On branches where [https://bugzilla.mozilla.org/show_bug.cgi?id=643704 bug 643704] has landed, adding the following in a '''mozconfig-extra''' or '''mozconfig-extra-$platform''' file will suffice:
mk_add_options MOZ_PGO=
On other branches, fool the system!
Include this in your patch.
diff --git a/client.mk b/client.mk
--- a/client.mk
+++ b/client.mk
@@ -210,5 +210,5 @@ else
endif
-profiledbuild::
+Xprofiledbuild::
$(MAKE) -f $(TOPSRCDIR)/client.mk build MOZ_PROFILE_GENERATE=1
$(MAKE) -C $(PGO_OBJDIR) package
@@ -352,5 +352,5 @@ endif
# Build it
-build:: $(OBJDIR)/Makefile $(OBJDIR)/config.status
+profiledbuild:: $(OBJDIR)/Makefile $(OBJDIR)/config.status
$(MOZ_MAKE)
== Server Status ==
