1419944 - provide continuous integration testing of the branding options that we ship

Status: NEW

(Firefox Build System :: General, enhancement)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Since we added --enable-official-branding as an option back in 2004 in bug 237596, I've had it in my own mozconfig since I knew that we didn't have any continuous integration testing that it compiled, and I thought it was important to notice any build failures before we got to needing it.

It's certainly possible for the build to break.  See bug 1416968 for a recent example, which I know RyanVM hit as well.

Depending on a few developers to detect breakage in something that's in the critical path to shipping Firefox is far from ideal.  Instead, we should have continuous integration testing that all of the branding options that we are going to ship are working.  This means that on central-ish repositories we should be testing that the branding that we'll use for nightly, dev edition, beta, and release works, and on beta-ish repositories we should test all of those except the branding we use for nightly.  (Of course, we're already testing one of them -- we just need to make sure we're testing the others, and the right set for appropriate trees.)

Comment 1

[Gregory Szorc [:gps]]

Since CI configuration is in-tree these days and this has to do with build configurations, let's track this in the build component.