Closed Bug 1174670 (Flame_L_PVT) Opened 6 years ago Closed 5 years ago

[Flame L] Create Lollipop based builds for master/2.2 to Taskcluster

Categories

(Taskcluster :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: hcheng, Unassigned)

References

Details

(Whiteboard: [b2g-build-support])

We need to create Flame L builds against pvtbuilds server for 2.2 and mozilla-central.
Depends on: 1153155
I'm pretty sure this is something for James' team at this point...
Component: General Automation → TaskCluster
Product: Release Engineering → Testing
QA Contact: catlee
Hi Josh, do you know who can handle this?
Flags: needinfo?(jocheng)
Hi Viral,
Do you know who can help?
Thanks!
Flags: needinfo?(jocheng) → needinfo?(vwang)
Hi Josh,

Maybe the information in this comment can help.
https://bugzilla.mozilla.org/show_bug.cgi?id=1055305#c16

Once we have manifest for flame-l (bug 1153155), we can pass it to release team for help :)
Flags: needinfo?(vwang)
Depends on: 1177361
Flags: needinfo?(nhirata.bugzilla)
Blocks: Flame_L
Alias: Flame_L_PVT
Since bug 1153155 already landed, we can have PVT for master now, but not for v2.2 (bug 1177361) so far.
See Also: → 1174336
Update the summary since the new build would be moved to TaskCluster.
@Wander, could you please help?
Flags: needinfo?(wcosta)
Summary: [Flame L] Create Lollipop based pvtbuilds for 2.2 → [Flame L] Create Lollipop based builds for mastrer/2.2 to Taskcluster
(In reply to Hermes Cheng[:hermescheng] from comment #6)
> Update the summary since the new build would be moved to TaskCluster.
> @Wander, could you please help?

Yeah, do you need OTA update for that?
Flags: needinfo?(wcosta)
Hi Wander, 
Yes, I think we still need OTA for Flame L as now not every Mozilla developers has Z3C which they will still to use Flame as development phone at beginning of 2.5. 
Thanks!
(In reply to Wander Lairson Costa [:wcosta] from comment #7)
> (In reply to Hermes Cheng[:hermescheng] from comment #6)
> > Update the summary since the new build would be moved to TaskCluster.
> > @Wander, could you please help?
> 
> Yeah, do you need OTA update for that?

Hi Wander,

As I know, we can only provide OTA to update a device from an older flame-l to the latest flame-l build (only updating gaia+gecko). Did you mean the same thing?
Flags: needinfo?(wcosta)
(In reply to Hermes Cheng[:hermescheng] from comment #9)
> (In reply to Wander Lairson Costa [:wcosta] from comment #7)
> > (In reply to Hermes Cheng[:hermescheng] from comment #6)
> > > Update the summary since the new build would be moved to TaskCluster.
> > > @Wander, could you please help?
> > 
> > Yeah, do you need OTA update for that?
> 
> Hi Wander,
> 
> As I know, we can only provide OTA to update a device from an older flame-l
> to the latest flame-l build (only updating gaia+gecko). Did you mean the
> same thing?

Yes, I did. If you look at the flame_kk tasks [0], there are tasks for OTA and non-OTA builds. That's because OTA tasks run only on mozilla-central, and the others run also on other brances.

[0] https://dxr.mozilla.org/mozilla-central/source/testing/taskcluster/tasks/builds
Flags: needinfo?(wcosta)
Spoke with wcosta, and he mentioned this is a releng issue that could take a while to put patches together to get going.

Selena, Could you find someone to help with this please other than Wander?
Flags: needinfo?(sdeckelmann)
Summary: [Flame L] Create Lollipop based builds for mastrer/2.2 to Taskcluster → [Flame L] Create Lollipop based builds for master/2.2 to Taskcluster
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #11)
> Spoke with wcosta, and he mentioned this is a releng issue that could take a
> while to put patches together to get going.
> 
> Selena, Could you find someone to help with this please other than Wander?

I met with Josh at Whistler and let the FxOS team know that we no longer have the people with expertise to implement this and managing emulator support needed to be a priority for FxOS itself. I will forward you the notes from that meeting directly.
Flags: needinfo?(sdeckelmann)
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
We have the same problem we had when moving from jb to kk: we will have two different builds for the same platform. Talking to bhearsum he advised to have one unique BUILD_TARGET for device target. There is already partial work on that (Bug 1166522), but we need to fix the build side to land this.

I will work on that.
Depends on: 1166522
Component: TaskCluster → General
Product: Testing → Taskcluster
Sorry for the churn; FYI, it might be good to hold off on this task.  We may be dropping Flame-L support and just going with Aries-L instead... This is to be determined sometime this week by Jonas Sicking, I believe.
Flags: needinfo?(wcosta)
Flags: needinfo?(sdeckelmann)
Flags: needinfo?(nhirata.bugzilla)
( oh oops.  sorry, not Jonas.  the discussion is still occuring for this particular topic, though we may just be dropping Flame-L support.  I will try to figure out when we have a final decision. )
Flags: needinfo?(sdeckelmann)
Flags: needinfo?(wcosta)
Whiteboard: [tc-build-support]
Assignee: wcosta → nobody
Status: ASSIGNED → NEW
Whiteboard: [tc-build-support] → [b2g-build-support]
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.