Closed Bug 885901 Opened 11 years ago Closed 11 years ago

figure out how to create "helix" builds manually

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

Product:
Firefox OS Graveyard
Component:
GonkIntegration
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: joduinn, Unassigned)

References

Details

we've been asked to generate "helix" builds for v1.1.1/v1.1HD. Before we can automate builds, we need instructions on how to build... hence this bug. 

From email thread, its unclear if we can use the same RIL for these device builds on this branch or not, so please clarify that also.


(If it helps for us to assign out a loaner machine, let us know and we'll make that happen.)
CCing mchen and kkuo who will be able to provide the necessary information.
kkuo, any progress on this?   can you get instructions to releng on how to build into the nightlies?
Flags: needinfo?(kkuo)
Hi! John, Tony,

The build process of helix device is as following.

First, you need to get android backup files of helix device and put it somewhere in build server(~/backup-img/helix-ics).
# export ANDROIDFS_DIR=~/backup-img/helix-ics
# git clone https://git.mozilla.org/b2g/B2G B2G_Helix
# cd B2G_helix
# BRANCH=v1.1.0hd ./config.sh helix
# ./build.sh

--
Keven
Flags: needinfo?(kkuo)
John, does this get your team what you need?  can we move forward on getting builds up this week?   We'd like to start testing it by tomorrow.
notes from email, to keep everyone in the loop.

tchung: we've got some (but not all) of the info we need to start generating builds. Once we get all the info, it'll take us a few days at least to stand up builds-per-checkin and nightly-builds for this device. 

mwu/kkuo: As no-one in RelEng has a helix phone, who can get us the backup/binary blob files from a helix phone? Also who can confirm what version of MozRIL to use? Also, if we need commercial RIL, do we use the same commercial RIL that we have for other devices or is there a new/different commercial RIL we need here?
Flags: needinfo?(tchung)
Flags: needinfo?(mwu)
Flags: needinfo?(kkuo)
I don't have a copy of the backup directory handy.

There is no such thing as a version of mozril. It comes bundled with every copy of gecko.

We'll want the commercial ril we've been using for v1.1 devices. It's no different.
Flags: needinfo?(mwu)
Hi! Tony,

Could you offer a place that I can upload the backup files?

--
Keven
Flags: needinfo?(kkuo)
Do we have a boot.img?
The other devices seem to have them, and they seem to differ per device.
(In reply to kkuo from comment #7)
> Hi! Tony,
> 
> Could you offer a place that I can upload the backup files?
> 
> --
> Keven

can you put it up on your people.mozilla.com account for now until releng pulls it?  or dropbox it too.
Flags: needinfo?(tchung)
Needinfo?ing Keven for the boot.img question in comment 8, plus this one:

The build in bug 885902 is dying on the absence of adb.
I'm trying to get that in PATH currently, but is it actually mandatory to use adb in the build, or can we get rid of that requirement?
Flags: needinfo?(kkuo)
(In reply to Aki Sasaki [:aki] from comment #10)
> The build in bug 885902 is dying on the absence of adb.
> I'm trying to get that in PATH currently, but is it actually mandatory to
> use adb in the build, or can we get rid of that requirement?

Hi Aki,

If you got the backup directory of helix and put it on the right place then extract_files.sh will skip to do actions related to adb commands and replace by checking backup directory directly.
(In reply to Aki Sasaki [:aki] from comment #8)
> Do we have a boot.img?
> The other devices seem to have them, and they seem to differ per device.

Please do not put the boot image in these builds. We'll need a gaia + gecko only flashing script like Leo.
Flags: needinfo?(kkuo)
(In reply to Michael Wu [:mwu] from comment #13)
> Please do not put the boot image in these builds. We'll need a gaia + gecko
> only flashing script like Leo.

The case on leo is that we flashed the Fx OS image (from partner) into the device so what we do for updating b2g stuffs is to do "adb push" for gaia + gecko.

Currently the case on helix is that 
  1. device is still on Android image so we need to flash entire system.img/userdata.img and "also the boot.img" from Keven for initiating b2g process.
  2. device is updated to Fx OS already then you can just update the gaia + gecko.

In the future, we will discuss internally about whether we need to follow the procedures from Leo. This means that we will get whole images release from helix partner then flashing into device. Then we can just update the gaia + gecko only.

Is this align with all yours?
Thanks.
I have a build ( https://bugzilla.mozilla.org/show_bug.cgi?id=885902#c9 ), and will land when I get approval in bug 885902.

I'm going with not uploading boot.img per comment 13; if that changes I'll need to upload it and update the patches in bug 885902.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
(In reply to Marco Chen [:mchen] from comment #14)
> Currently the case on helix is that 
>   1. device is still on Android image so we need to flash entire
> system.img/userdata.img and "also the boot.img" from Keven for initiating
> b2g process.
>   2. device is updated to Fx OS already then you can just update the gaia +
> gecko.
> 

We can't test reliably if we don't start on a FFOS base image though - there's a number of B2G specific fixes we need. We should make sure we get a base image based on b2g/ics_strawberry as soon as it can be made available and use gaia + gecko only flashing on top of that.
(In reply to Michael Wu [:mwu] from comment #16)
> We can't test reliably if we don't start on a FFOS base image though -
> there's a number of B2G specific fixes we need. We should make sure we get a
> base image based on b2g/ics_strawberry as soon as it can be made available
> and use gaia + gecko only flashing on top of that.

Thanks for the confirmation.
We are on going to discuss with partner for image based b2g/ics_strawberry build.
(In reply to Marco Chen [:mchen] from comment #17)
> (In reply to Michael Wu [:mwu] from comment #16)
> > We can't test reliably if we don't start on a FFOS base image though -
> > there's a number of B2G specific fixes we need. We should make sure we get a
> > base image based on b2g/ics_strawberry as soon as it can be made available
> > and use gaia + gecko only flashing on top of that.
> 
> Thanks for the confirmation.
> We are on going to discuss with partner for image based b2g/ics_strawberry
> build.

Hi marco, any update on this?   I'm losing precious testing time each day that we're waiting for builds to work.
Hi Tony,

Thanks for the reminding here and I miss to give you information about image releasing.

1. Currently chip vendor didn't be ready for releasing 1.1.0hd so we can't get formal release from our partner now. (I will check with PM for exact date then feedback to via email).

2. So I would recommend you to use our own build for testing in first stage.
(In reply to Marco Chen [:mchen] from comment #19)
> Hi Tony,
> 
> Thanks for the reminding here and I miss to give you information about image
> releasing.
> 
> 1. Currently chip vendor didn't be ready for releasing 1.1.0hd so we can't
> get formal release from our partner now. (I will check with PM for exact
> date then feedback to via email).
> 
> 2. So I would recommend you to use our own build for testing in first stage.

hi marco,

please keep pushing on point 1 with the vendor.   We need to have the build as close to production setup as quickly as possible.

for point 2, can you build me a tryserver build for this?   I would trust you doing it much more than me.  you can post it at: https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/try-builds/

Thanks
Flags: needinfo?(mchen)
(In reply to Tony Chung [:tchung] from comment #20) 
> for point 2, can you build me a tryserver build for this?   I would trust
> you doing it much more than me.  you can post it at:
> https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/try-builds/
> 

Hi Tony,
As I know that try server for B2G builds are only for generic/emulator/unagi and pandaboard. There is no build for Helix so I am not sure what do you mean for this. Thanks for your input first.
Flags: needinfo?(mchen)
(In reply to Marco Chen [:mchen] from comment #21)
> (In reply to Tony Chung [:tchung] from comment #20) 
> > for point 2, can you build me a tryserver build for this?   I would trust
> > you doing it much more than me.  you can post it at:
> > https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/try-builds/
> > 
> 
> Hi Tony,
> As I know that try server for B2G builds are only for generic/emulator/unagi
> and pandaboard. There is no build for Helix so I am not sure what do you
> mean for this. Thanks for your input first.

I was under the impression that we can post device images there as well, but i guess not.  Releng would know better if thats true or not.  Anyway, please keep working on getting us a base image from partner.  in the meantime, i'll see what we can do to build, and ask you and keven for help if needed.
We explicitly have not turned on try device builds, since there are concerns over keeping these device builds very locked down.
(In reply to Aki Sasaki [:aki] from comment #23)
> We explicitly have not turned on try device builds, since there are concerns
> over keeping these device builds very locked down.

Okay thanks for the clarification.

With Keven's help from comment 3, we were also able to self build and flash the device.   this offers us a second solution to the releng builds.
Status: RESOLVED → VERIFIED
Blocks: 903661
You need to log in before you can comment on or make changes to this bug.