840839 - generate "hamachi" builds for B2G

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Please generate nightly builds for "buri" devices. 

open questions: 

0) what branches are these supported on? I'd guess v1.1 and beyond, but looking for official confirmation.

1) do we also need per-checkin builds?

2) do we need to generate updates? If yes, how to make these updates available without complicating updates being generated for other devices.

3) what locales are to be included? (although this feels like wider question about locales for v1.1, noting here to track).

Comment 1

[Al Tsai [:atsai]]

We need to raise it to higher priority and get it done.

Michael, can you help on it?

For the open questions

0) we'll need v1.0.1 (gaia:v1.0.1/gecko:b2g18-v1.0.1), v1.1 (v1-train/b2g18).

1) I think nightly build should be enough.

For question 2 & 3, looking for someone to answer.
I'll try to find the answer and come back to you.

Comment 2

[Tony Chung [:tchung]]

I'm told by James that Keven kuo has gotten this ported successfully.   If thats the case, what is needed to get releng the build information they need to move forward?

Last i heard, 100 Buri devices were enroute to MV and TW this week.

Comment 3

[Al Tsai [:atsai]]

Yes, I think Keven Kuo can also help on this.

And yes, the buri devices should arrive at the end of this week.

Comment 4

[Michael Wu [:mwu]]

We've had a port for this for a while under "hamachi". I'm going to clean up the port a bit and forward the necessary information to releng.

Comment 5

[Al Tsai [:atsai]]

:mwu,
Should we change the code name from hamachi to buri to reduce unnecessary misunderstanding.

Comment 6

[Michael Wu [:mwu]]

(In reply to Al Tsai [:atsai] from comment #5)
> :mwu,
> Should we change the code name from hamachi to buri to reduce unnecessary
> misunderstanding.

Our port names are already separate from the actual device names. It's also a bit painful to switch port names - it involves a lot of changes in different places without much gain.

Comment 7

[Chris AtLee [:catlee]]

Attachment: gecko configs for hamachi

Comment 8

[Chris AtLee [:catlee]]

Attachment: buildbot-configs for hamachi

Comment 9

[Chris AtLee [:catlee]]

Attachment: mozharness configs for hamachi

Comment 10

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

Comment on attachment 734914 [details] [diff] [review]
gecko configs for hamachi

Looks fine compared to inari, rubber stamp on the sources.xml.

Comment 11

[Alex Keybl [:akeybl]]

Given comment 1, marking as a NPOTB tef+ bug so that this can land to all active branches up to v1.0.1.

Comment 12

[Chris AtLee [:catlee]]

in production

Comment 13

[Chris AtLee [:catlee]]

Attachment: turn hamachi on v101

we'll need gecko changes too

Comment 14

[Chris AtLee [:catlee]]

Attachment: hamachi configs for v101

Comment 15

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/b35eed1ab45e

Comment 16

[Chris AtLee [:catlee]]

live on mozilla-b2g_v1_0_1 now