The current Flame nightly is experiencing instability and other issues. Until the issues are rectified, it was suggested that we want to turn off the nightly update so that users are not in a bad state. Bug 1046790 is one example, but it has also been reported that all downloaded apps are failing.
I've shut off updates completely for the nightly b2g channel. I'd like to repoint at the last known good build though, rather than have them completely off. I've pinged Marcia on IRC about that. I'll update the bug when it's done.
Assignee: nobody → bhearsum
For RelEng: What I did was change the rule that is product=B2G, channel=nightly to point at the "No-Update" mapping. If Marcia finds a known good build, the mapping should be changed to point at the dated release that matches it. When we're ready to repoint at the latest nightly, the rule should be pointed back to B2G-mozilla-central-nightly-latest
Assignee: bhearsum → nobody
[Blocking Requested - why for this release]: Blocks smoke test from doing OTA's. QAWanted to find the last working nightly we can point to.
blocking-b2g: --- → 2.1?
Keywords: qaurgent, qawanted, smoketest
(In reply to Peter Bylenga [:PBylenga] from comment #3) > [Blocking Requested - why for this release]: > Blocks smoke test from doing OTA's. > > QAWanted to find the last working nightly we can point to. Last working nightly URL: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame/2014/07/2014-07-30-16-02-00/
Keywords: qaurgent, qawanted
Pointed updates at the B2G-mozilla-central-nightly-20140730160200 blob. I suspect we've had another nightly at 4pm with the appropriate backouts, but lets wait for QA to confirm that.
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame/2014/08/2014-08-01-04-03-26/ build addresses the issues in the earlier build, so we can safely turn back updates and have them update to that build.
The update rule points at B2G-mozilla-central-nightly-latest now, which is currently the 2014-08-01-04-03-26 build.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.