bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Set a smaller value for DOWNLOAD_BACKGROUND_INTERVAL for non official builds

RESOLVED FIXED in mozilla1.9.2a1



Application Update
10 years ago
9 years ago


(Reporter: rstrong, Assigned: rstrong)



Firefox Tracking Flags

(Not tracked)



(1 attachment)

When downloading an complete update for a nightly build the interval is way too long and will take hours (around 5?) to complete and often it will be the next day before the download has completed. By changing DOWNLOAD_BACKGROUND_INTERVAL from 600 to 60 for non official builds (e.g. nightly builds) the approximate time to complete should be under an hour.
Probably best to key on either the channel or official branding.
MOZILLA_OFFICIAL means "anything built on any Mozilla tinderbox" so you don't want that.
Yea... I'm a bit slow and under the weather today
If we're going down this road (and it's a good road to tread), then it'd be worth considering shortening app.update.interval too. The default check of once a day means you end up with more complete updates than is convenient for frequent nightly use. We'd have to check if that'd impact on metrics though.
and I notified metrics when I made the change
Pardon me, I really should pay more attention. That was in Bug 324121 ftr.
No worries
This is only affecting nightly builds and not releases, right?
Created attachment 361827 [details] [diff] [review]
patch rev1

I went with a pref since other apps may want to specify a custom value.
Assignee: nobody → robert.bugzilla
Attachment #361827 - Flags: review?(mconnor)


10 years ago
Attachment #361827 - Flags: review?(mconnor) → review+
I'll land this after the mozilla-central tree is in better shape.

btw: I gave Justin a heads up about this change for nightly updates as well.
cc'ing a bunch of people in case they are interested in adding this pref for their app updates.

Comment 15

10 years ago
It seems wrong for this to depend on branding (rather than, say, channel).  I think depending on branding will make alphas behave like nightlies and betas behave like releases, which might not be what we want.
Well, the pref can be set to whatever number and for whatever type of build it wants and if an app chooses not to we fallback to the number of seconds we've been using. I agree that it *might* be nice to have a new way of setting this but that can be said about several of the prefs set in the branding prefs file as well as other code that is different based on the type of build.
Pushed to mozilla-central
Last Resolved: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.2a1
You need to log in before you can comment on or make changes to this bug.