1194206 - Switch gaia 2.2(r) builds to use 2.2 l10n repos

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Axel Hecht [:Pike]]

My suspicion is that we need the fix at http://hg.mozilla.org/build/buildbot-configs/file/c297056a6bcf/mozilla/b2g_config.py#l1373 and http://hg.mozilla.org/build/buildbot-configs/file/c297056a6bcf/mozilla/b2g_config.py#l1395.

Instead of https://hg.mozilla.org/gaia-l10n, it should pick up http://hg.mozilla.org/releases/gaia-l10n/v2_2/

Repos are up and ready, including git mirrors (do we need something for that in any kind of config file?)

Comment 1

[Delphine Lebédel]

Pike: who are we waiting for an answer on this?

Comment 2

[Axel Hecht [:Pike]]

Release engineering

Comment 3

[Théo Chevalier]

Hi Hal,

do you have the answer to question in comment #0 ? If you don't, could you suggest someone that does?

This switch is blocking different things

Thanks!

Comment 4

[hwine]

It's unclear what the request is here. As the links in comment 0 show, 2.2r is currently using the same l10n repos as 2.2. Are you:
 - asking for 2.2r to use different than 2.2? (never done before)
 - asking for BOTH 2.2 & 2.2r to be switched to use the 2.2 repos
 - something else

Also, once we've done those changes, you do need to update all the in tree manifests as well. This mxr query will show you the pattern:
  http://mxr.mozilla.org/mozilla-b2g28_v1_3t/search?string=gaia-l10n%2Fv1_3&find=&findi=&filter=%5E%5B%5E%5C0%5D*%24&hitlimit=&tree=mozilla-b2g28_v1_3t
(I can't show you in the 2.2 repo, because that still uses https://hg.mozilla.org/gaia-l10 )

What is the ask here?

Comment 5

[Théo Chevalier]

Hi Hal, let me try to clarify what we need :)

(In reply to Hal Wine [:hwine] (use NI) from comment #4)
>  - asking for BOTH 2.2 & 2.2r to be switched to use the 2.2 repos

Yes, we need both branches to start using the 2.2 repos created in bug 1186618


> 
> Also, once we've done those changes, you do need to update all the in tree
> manifests as well. This mxr query will show you the pattern:
>  
> http://mxr.mozilla.org/mozilla-b2g28_v1_3t/search?string=gaia-
> l10n%2Fv1_3&find=&findi=&filter=%5E%5B%5E%5C0%5D*%24&hitlimit=&tree=mozilla-
> b2g28_v1_3t
> (I can't show you in the 2.2 repo, because that still uses
> https://hg.mozilla.org/gaia-l10 )

This is exactly what need to be changed, the manifests should stop pulling strings from gaia-l10n for 2.2.

For any device, all builds running 2.2 or 2.2r code should start using releases/gaia-l10n/v2_2 repos.

So, I think the manifests thing was the missing part Pike was asking about in comment #0 :)

Let us know if there is still something unclear or if you need anything from our side

Comment 6

[hwine]

Attachment: v2.2-l10n.patch

Comment 7

[hwine]

Comment on attachment 8651192 [details] [diff] [review]
v2.2-l10n.patch

https://hg.mozilla.org/build/buildbot-configs/rev/42635b678c73

Comment 8

[Delphine Lebédel]

What's needed here so that we can close this bug please? We're already mid-cycle for 2.5 and are still blocked.

Comment 9

[hwine]

We're waiting on a standard reconfig. Often they occur daily, we're in an August lull -- we're starting one shortly.

Comment 10

[Release Engineering SlaveAPI Service]

In production: https://hg.mozilla.org/build/buildbot-configs/rev/42635b678c73

Comment 11

[Axel Hecht [:Pike]]

Hal, has everything needed here landed? If so, can you mark this fixed? Thanks.

Comment 12

[Delphine Lebédel]

ni on Hal for question in comment 11

Comment 13

[hwine]

(In reply to Axel Hecht [:Pike] from comment #11)
> Hal, has everything needed here landed? If so, can you mark this fixed?
> Thanks.

Assuming this question means you're getting everything you need, so closing.

If you are not, please reopen with specifics of what is not working.