751703 - release_sanity.py needs to check locales/locale repos from a different url

Status: RESOLVED WONTFIX

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

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

as per today's meeting with Axel, we'll use something like https://l10n.mozilla.org/shipping/l10n-changesets?av=fx13 for Firefox l10n_changesets for rapid betas so release_sanity.py (if we still use it for rapid betas) will need to be updated to check there instead of a dashboard milestone.

Comment 1

[Axel Hecht [:Pike]]

Here's the action items as I see them:

- use https://l10n.mozilla.org/shipping/l10n-changesets?av=fx13 and friends to get the hg revision to use per locale
- possibly/probably don't tag
- depending on where the changesets are stored, the release_sanity might fail due to new sign-offs being taken for the application version, i.e., firefox 13. (changesets are landed in buildbot-configs, build is triggered a few hours later, I took more sign-offs in the meantime)
-- maybe drop the sanity check alltogether

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

(In reply to Axel Hecht [:Pike] from comment #1)

> - possibly/probably don't tag

the plan of the moment seems to be that while we won't tag the repos, we will store all the changesets used for a particular build in another repo and will tag that commit.  this will minimize the tagging churn on repos that are more public/shared and keep it to a manifest that only automation really cares about.

> - depending on where the changesets are stored, the release_sanity might
> fail due to new sign-offs being taken for the application version, i.e.,
> firefox 13. (changesets are landed in buildbot-configs, build is triggered a
> few hours later, I took more sign-offs in the meantime)

as long as the changeset exists in the repo, the sanity check should find it and assert that it is present.  this is all we need in order to start automation and not be concerned that a locale will fail on a missing changeset (or empty repo)

> -- maybe drop the sanity check alltogether

it's a valid need to check that the changesets and repos are present and accounted for, no need to drop the sanity we hold on to tenuously :)

Comment 3

[[e-mail] (:bhearsum)]

Rapid Beta priority fell, we'll pick this up at some point when we start working on it.

Comment 4

[Rail Aliiev [:rail]]

We are changing the way how we retrieve l10n from elmo