Closed Bug 609790 Opened 14 years ago Closed 14 years ago

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christian, Assigned: fox2mike)

References

Details

+++ This bug was initially created as a clone of Bug #587998 +++

+++ This bug was initially created as a clone of Bug #580180 +++

Redirect http traffic from http://ftp.mozilla.org/pub/firefox/nightly/4.0b*-candidates/* to http://wiki.mozilla.org/Releases/Firefox_4.0b*

Let's do this a bit smarter this time and wildcard the version so we don't have to do it again....
Assignee: server-ops → shyam
Done.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
RewriteRule ^/pub/mozilla\.org/firefox/nightly/4\.0b(.*)-candidates/ http://wiki.mozilla.org/Releases/Firefox_4.0b$1 [R=302,L]
Blocks: 596259
Two things.

* What are we trying to fix by not allowing people to download candidate builds?  Is it because they are not QAed?

* What URL can we provide for testdays? Can we remove the redirect during that day? Can we provide a URL that only works during some time?

Currently this is the scenario for URLs

* 550 HTTP error (only for .exe files)
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b7-candidates/build1/win32/en-US/Firefox%20Setup%204.0%20Beta%207.exe
* Redirect in place
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b7-candidates/build1/win32/en-US/Firefox%20Setup%204.0%20Beta%207.exe
* Being used by testday as stop-gap (IT ain't happy about it)
http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b7-candidates/build1/win32/en-US/Firefox%20Setup%204.0%20Beta%207.exe
It was my understanding the FTP links (ftp://) would work fine (as before). That's not the case?
This morning testday people were not being able to provide testers Windows builds (see bug 609888).
In bug 609888#c7, Dave mentions the following:
"I changed the block rule to specifically block Beta 6 again.  It'll need to be
changed to Beta 7 when the files get moved to /releases/ for the public
release."

What I understand is that we want to avoid any news site or blogs to point people to ftp and this seems to happen when we get close to release; is this correct?

In the future, could we also track bugs like this under the release tracking bug to make it easier to be found (specially for the releng running the release)? Thanks!
(In reply to comment #4)
> It was my understanding the FTP links (ftp://) would work fine (as before).
> That's not the case?

It was not the case until a little ago.

The config had:
deny_file={Firefox Setup 4.0 Beta *.exe,Firefox Setup 3.6.10.exe}
and justdave just fixed by removing the wildcard and blocking only Beta 6's exe files.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.