1 Mozilla Build Verification Scripts
8 updates -> AUS and update verification
9 l10n -> l10n vs. en-US verification
10 common -> useful utility scripts
17 does a low-level check of all advertised MAR files. Expects to have a
18 file named all-locales, but does not (yet) handle platform exceptions, so
19 these should be removed from the locales file.
21 prints errors on both STDOUT and STDIN, the intention is to run the
22 script with STDOUT redirected to an output log. If there is not output
23 on the console and an exit code of 0 then all tests pass; otherwise one
28 1) download update.xml from AUS for a particular release
29 2) download the partial and full mar advertised
30 3) check that the partial and full match the advertised size and sha1sum
31 4) downloads the latest release, and an older release
32 5) applies MAR to the older release, and compares the two releases.
34 Step 5 is repeated for both the complete and partial MAR.
36 Expects to have an updates.cfg file, describing all releases to try updating
40 Valid Platforms for AUS
53 unpacks an en-US build for a particular release/platform, and
54 then unpacks and compares all locales for that particular release/platform.
56 Expects to have a file named all-locales, but does not (yet) handle platform
57 exceptions, so these should be removed from the locales file.
59 Best practice is to take a directory full of diffs for a particular release
60 and compare to a directory full of diffs for the current release, to see
61 what l10n changes have occurred. For maintenance releases, this should