Closed Bug 1540046 Opened 6 years ago Closed 6 years ago

No Firefox updates being advertised - 68.0a1 (2019-03-27)

Categories

(Release Engineering :: Release Automation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1540132

People

(Reporter: mozilla-crowdicity.wadmol, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Go to Preferences > Nightly Updates and click on Check for updates

Actual results:

It says Nightly is up to date. I had to download the latest version. I will let you know if I don't receive an update tonight - IST.

Expected results:

If there is an issue, it should be mentioned that manual update is required

Has STR: --- → yes
Component: Untriaged → Application Update
Product: Firefox → Toolkit
Summary: Firefox updates broken on 68.0a1 (2019-03-27) → No Firefox updates being advertised - 68.0a1 (2019-03-27)

The update url doesn't have an update advertised
https://aus5.mozilla.org/update/6/Firefox/68.0a1/20190327175114/WINNT_x86_64-msvc-x64/en-US/nightly/Windows_NT 10.0.0.0.17134.648 (x64)/ISET:SSE4_2,MEM:32620/default/default/update.xml?force=1

Component: Application Update → Release Automation: Updates
Product: Toolkit → Release Engineering
QA Contact: mtabara
Version: 68 Branch → unspecified

This is likely due to Bug 1540132.

I could be wrong but I seem to recall that there was some discussion of sending an email to release-drivers (perhaps dev-platform as well) when something broke updates. If not, sending an email would be helpful so it is simpler to triage bug reports for no updates being advertised and to lessen additional bug reports.

Duping to the fixed bug in Comment 2. rstrong I agree with you it should probably be better communicated. From what I can see, there was some slack discussion this morning in at least one channel and the issue was also noted on the Firefox Nightly Twitter feed.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Component: Release Automation: Updates → Release Automation
You need to log in before you can comment on or make changes to this bug.