Making a tryserver build as close as possible to a release build

[Benjamin Smedberg]

For a user research project, I am trying to make a tryserver build which
is close to a release build, at least in terms of user perception: it
should have official release branding, have the crashreporter on by
default. I don't think PGO is necessary, though ;-)

The build should not have an update channel.

What set of mozconfig/tryserver options would I use to get this?

I know about
http://mxr.mozilla.org/mozilla-central/source/browser/config/mozconfigs/win32/release
but I'm not exactly sure how to use that in terms of tryserver.

--BDS

[Ehsan Akhgari]

From the build logs for a Windows opt build on try, you can see this
command running:

'python' 'e:/builds/moz2_slave/try-w32/tools/buildfarm/utils/retry.py'
'-s' '1' '-r' '5' '-t' '1260' 'bash' '-c' 'if [ -f
"browser/config/mozconfigs/win32/nightly" ]; then
echo Using in-tree mozconfig; cp
browser/config/mozconfigs/win32/nightly .mozconfig;
else echo Downloading mozconfig;
wget -O .mozconfig
http://hg.mozilla.org/build/buildbot-configs/raw-file/production/mozilla2/win32/try/nightly/mozconfig;
fi'

Which tells me that you should be able to just copy over the release
mozconfig you pointed at to browser/config/mozconfigs/win32/nightly.

Cheers,
Ehsan

[Ben Hearsum]

I think copying that mozconfig to
browser/config/mozconfigs/win32/nightly should be all you need to
do...Note that some behaviour is dependent on the channel set, though
(https://mxr.mozilla.org/mozilla-central/search?string=MOZ_UPDATE_CHANNEL),
so you may need to hack those parts of the build system or set the
channel if you care about those.