The default bug view has changed. See this FAQ.

Firefox Nightly and Aurora updates not publishing automatically

RESOLVED FIXED

Status

Release Engineering
Releases
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: ashughes, Unassigned)

Tracking

unspecified

Firefox Tracking Flags

(firefox39+ fixed, firefox40+ fixed)

Details

I've been seeing reports on nightly-testers@lists.mozilla.org that updates are not working for Firefox 39.0a1 since Friday. I did some checking on my Mac and confirmed that my Nightly build (2015-03-20) is not finding any updates despite there being a newer build (2015-03-22) on the ftp server. I turned on logging and AUS:SVC reports "number of updates available: 0".

Here is the URL:
https://aus4.mozilla.org/update/3/Firefox/39.0a1/20150320030211/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/nightly/Darwin%2014.1.0/default/default/update.xml?force=1
This is blocked by bug 1144985
Depends on: 1144985

Comment 2

2 years ago
I can confirm this bug using Windows 7 64-bit: my Nightly build (2015-03-20) doesn't find new updates.
Duplicate of this bug: 1146155
status-firefox39: --- → affected
tracking-firefox39: --- → +

Comment 4

2 years ago
Just got the update window. New build: 20150322030216.

Comment 5

2 years ago
Looks like things are set for at least the next month.  Somebody has set Aurora and Nightly back to the ftp.mozilla.org location instead of the CDN, which is why we weren't getting updates before.

https://bugzilla.mozilla.org/show_bug.cgi?id=1144985#c14

One has to wonder, if the Nightly and Aurora updates are fubar, can we really expect the release and beta updates to be smooth?  I guess we will be finding out, one way or another.
(In reply to Bryan Price from comment #5)
> Looks like things are set for at least the next month.  Somebody has set
> Aurora and Nightly back to the ftp.mozilla.org location instead of the CDN,
> which is why we weren't getting updates before.
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1144985#c14
> 
> One has to wonder, if the Nightly and Aurora updates are fubar,

Fubar is too strong a word. They're not totally broken, they just require manual work every morning to get them served (because they publish automatically pointing at ftp, not at the CDN).

> can we
> really expect the release and beta updates to be smooth?  I guess we will be
> finding out, one way or another.

Beta and Release are always served from the CDN. I would be shocked if they weren't served quickly and effectively.
Summary: No updates available for Firefox 39.0a1 → Firefox Nightly and Aurora updates not publishing automatically

Comment 7

2 years ago
(In reply to Ben Hearsum [:bhearsum] from comment #6)
> (In reply to Bryan Price from comment #5)
> > One has to wonder, if the Nightly and Aurora updates are fubar,
> 
> Fubar is too strong a word. They're not totally broken, they just require
> manual work every morning to get them served (because they publish
> automatically pointing at ftp, not at the CDN).

Thanks, Ben.  Yeah, it probably is too strong.  Still, I would have to download the .mar file myself, and figure out how to apply it.  Opening a .mar file (I assume that's the file we download for just the changes) on my computer starts Access, which wouldn't be conducive to patching Nightly.  So I would be forced to download the 43MB or so install every day that I wanted to keep updated.  (does a bit of Googling)  It looks like there are ways to manually patch, I'll read more when I have a chance.

> 
> > can we
> > really expect the release and beta updates to be smooth?  I guess we will be
> > finding out, one way or another.
> 
> Beta and Release are always served from the CDN. I would be shocked if they
> weren't served quickly and effectively.

I'll believe that.  

My thought is, the same day the original bug was filed, somebody filed a patch, and without much thought about what things need to be in shape to actually make the process anything close to being somewhat of a smooth one, the trigger was pulled (on a Friday!), and people are wondering what's going on.

I think that us Nightly users, programmers or no, are used to bustage.  It just gets weird when the bustage is more about the delivery system for updates than it is for the program itself.

It has been a bad week (indeed, a bad month and a half), and I'm probably acting out way more here than I should have.

My apologies.
status-firefox40: --- → affected
tracking-firefox40: --- → +
Ben, do you think we need to be tracking this or do you have it in hand?  Comment 5 mentions this was set for the next month, and that was a month ago.
Flags: needinfo?(bhearsum)
Deferingto Rail on this, but I'm pretty sure it's fixed already...
Flags: needinfo?(bhearsum) → needinfo?(rail)
Yeah, this is fixed by bug 1144985
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(rail)
Resolution: --- → FIXED
status-firefox39: affected → fixed
status-firefox40: affected → fixed
You need to log in before you can comment on or make changes to this bug.