Closed Bug 754290 Opened 12 years ago Closed 12 years ago

decide whether or not we'll be pushing to internal mirrors for rapid betas

Categories

(Release Engineering :: Release Automation: Other, defect, P3)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

Details

Nick and I chatted a little bit yesterday about whether or not we should be pushing to internal mirrors for rapid betas. The basic concern is that pushing so much data to them up to 7 times per week will be more than they can handle and/or not worth the effort. If the new ftp.m.o can support the load, it would be simpler/quicker to serve beta users off of it. We should talk with IT about whether or not that's possible.

If we do go that route we'll either need to stop pushing betas to releases/ and adjust the bouncer .ini templates, or modify the rsyncd exclude files to prevent betas from getting on internal mirrors.
Priority: -- → P3
In CDN-land this is a non-issue, they all go onto the CDN.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.