Closed Bug 1203251 Opened 10 years ago Closed 9 years ago

Use periodic OTA builds to submit to balrog and turn off B2G buildbot nightlies

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mshal, Unassigned)

Details

The nightly Flame/Nexus device builds still run on buildbot rather than Taskcluster. Until they are ported to TC, it would be helpful to have them upload their artifacts to TC similar to fx_desktop_build/desktop_l10n/etc. CC'ing :sdeckelmann in case porting these is imminent anyway.
Looks like all Nexus builds are still in buildbot too, not just the nightlies. Those should be moving to TC anyway in bug 1187946. I'm still trying to figure out if the buildbot nightlies are even still needed, or if they are superseded by the Taskcluster OTA builds.
Assignee: mshal → nobody
Component: Mozharness → General Automation
QA Contact: jlund → catlee
Summary: b2g_build.py invoked from buildbot should upload to TC → Use periodic OTA builds to submit to balrog and turn off B2G buildbot nightlies
With bug 1187946 in progress, I believe all that remains for B2G builds to be fully indexed are the buildbot nightlies. I think the plan there is to make the OTA builds (which are already in Taskcluster) the official ones by having them only periodically (2x a day) get submitted to balrog. We could potentially just use the opt builds for this, and have a different task that takes the latest opt build and submits it to balrog as the OTA. Once that is up, we could turn off buildbot nightlies. Since that doesn't seem too far off, I don't think there's a point to modifying b2g_build.py to upload files to Taskcluster since all the b2g builds will be in Taskcluster anyway.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.