789047 - Run update verify against some partner repacks

Status: NEW

(Release Engineering :: Release Automation, defect, P3)

Description

[Rail Aliiev [:rail]]

We should run update verify checks against some partner repacks to make sure that those get updates properly. We hit a problem on Mac because repacks imply recreating of Firefox binary for every repack.

Comment 1

[[e-mail] (:bhearsum)]

This should be easier to do now that we have the update verify dumper. Here's one idea:
* Choose a hardcoded list of partners/locales/platforms to test. Lets say, euballot+de/en-GB/ru+win32 and tonline+de+linux32/mac/win32.
* Change 'channel' to be a release_key rather than a global_key in UpdateVerifyConfig (https://github.com/mozilla/build-tools/blob/master/lib/python/release/updates/verify.py#L16)
* Add an extra "release" for each of partners in this loop: https://github.com/mozilla/build-tools/blob/master/scripts/updates/create-update-verify-configs.py#L115 -- the only thing different from the vanilla would be the channel.
* The update verify scripts should "just work".

I thought about adding this information to the patcher config or adding a new "partners" value to the update verify configs. Both of these are made difficult because of the fact that each partner has a different set of locales, so you can't simply say that "tonline" or "euballot" is a partner channel for 15.0, because you'd need to store a separate list of platforms/locales or exceptions for both.

Comment 4

[Mihai Tabara [:mtabara]⌚️GMT]

Do we still want this, in the new TC world?

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

It's still a fair request to add test coverage for these builds.