Closed Bug 1260682 Opened 9 years ago Closed 9 years ago

hg.m.o shouldn't advertise s3 bundles that were not uploaded to s3 successfully

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Product:
Developer Services
Component:
Mercurial: hg.mozilla.org
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1260681

People

(Reporter: hwine, Unassigned)

References

Details

when _all_ S3 uploads failed in bug 1260652, hg.m.o still advertised bundles as present from S3. Probably better to both: a) holler long and loud about S3 upload failure b) consider falling back to serving bundles from hg.m.o Having the server advertise bundles that are not available is a tree closing event.
I'll address both these things in bug 1260681. The old bundles are deleted by an S3 bucket policy 7 or 14 days after initial upload. So if we fail to upload, we should just not change the manifest file and the old bundles will continue working. We'd have 7 days to fix upload failures before the server starts lying about bundles.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.