Closed
Bug 1224357
Opened 9 years ago
Closed 8 years ago
Fix Aries dogfood for mozilla central.
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhirata, Unassigned)
References
Details
(Keywords: qablocker)
Currently : 1) Dogfood channel is getting Nightly OTAs which is causing bug 1217490 to occur. We have to : 1) switch Aries-OTA to update the Balrog release: B2G-mozilla-central-nightly-latest 2) switch Aries-Dogfood to update the Balrog release: B2G-gecko-nightly-latest location of aries OTA : https://tools.taskcluster.net/index/artifacts/#gecko.v1.mozilla-central.latest.linux.aries-ota/gecko.v1.mozilla-central.latest.linux.aries-ota.debug location of aries DOGfood : https://tools.taskcluster.net/index/artifacts/#gecko.v1.mozilla-central.latest.linux.aries-dogfood/gecko.v1.mozilla-central.latest.linux.aries-dogfood.debug
Reporter | ||
Comment 1•9 years ago
|
||
Looks like Aries OTA is pointing to B2G-mozilla-central-nightly-latest do to wcosta's patch. Bug 1223950 We still need a separate release or a way to separate a dogfood build versus a nightly build.
Summary: Fix Aries dogfood and nightly builds for mozilla central. → Fix Aries dogfood for mozilla central.
Reporter | ||
Comment 2•9 years ago
|
||
To note, It turns out that in order for the IMEI whitelist portion to appear, the end user needs to be on a dogfood build. 1) We need the server fixed to point to the right build first. 2) We also need the whitelisting portion to be finished. 3) then people can update to the dogfood channel and then try to update... if they don't receive updates they probably aren't on the whitelist and then we need to clean that mess up. 4) for the people who shouldn't be whitelisted, they would need to switch back to nightlies... At least that's the way that it currently stands unless we change something in the client side on the dogfood to have everyone report their IMEI in a hash first and then switch over people who are white listed... We need to work that detail out with releng, taskcluster, dev, and qa first to make sure people are on the same page on what we're going to do and how we're going to switch them over before we implement this because it's going to be utter chaos with no one knowing what to do otherwise. And we should do this in a separate bug than this.
Reporter | ||
Comment 3•9 years ago
|
||
Filed bug 1224725 to handle the switch over issue. For now at the very least, we need to switch over the dogfood channel to the correct dogfood builds.
Reporter | ||
Comment 5•8 years ago
|
||
bug 1186944 is for the taskcluster side, this bug will track for the balrog update server side.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•