This would mean being able to handle the package installers and be able to drill down to the binary. Right now talos only knows how to handle tinderbox builds as zips, dmgs and tar.bz2.

Working with release builds pulled from: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/ So far, linux builds will not be an issue at all as they are in the same tar.bz2 as nightly/tinderbox builds.

Mac builds also not an issue, installed in a similar dmg structure to the nightly/tinderbox mac builds.

Windows release builds are packaged in an installer. We can use the command line interface to get around this: https://wiki.mozilla.org/Installer:Command_Line_Arguments Working on buildbotcustom patches to handle this option

Off by default. Will allow us adjust the addontester factory to test only release builds.

We'll need the firefoxInstallConfig.ini checked in as well - and then added to the build server to be downloaded when necessary. Not quite sure where we want this ini file to live, so I haven't specified a location yet. Probably will end up in the buildfarm utilities.

Fixed typo.

I'm missing some context here...why is this wanted/needed?

This is for addon performance testing - the requirement from the AMO team is that we test against what people are actually running on their own computers, which would be release builds.

Comment on attachment 481680 [details] [checked in]firefoxInstallConfig.ini firefoxInstallConfig.ini checked in changeset: 858:181fdc5605d1

Review carried over from previous patch.

Comment on attachment 490177 [details] [diff] [review] [checked in] add ability to buildbotcustom for intallation of release builds (take 3 - remove bitrot) changeset: 1213:c725f1a00335