Closed Bug 1408244 Opened 8 years ago Closed 8 years ago

Delete https://archive.mozilla.org/pub/thunderbird/releases/56.0b4/ and purge CDN caches

Categories

(Cloud Services :: Operations: Product Delivery, task)

Product:
Cloud Services
Component:
Operations: Product Delivery
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: jbuck)

Details

This is a particularly problematic release for the Thunderbird folks, they're up to build12 now. Could you please delete the contents of /pub/thunderbird/releases/56.0b4/ and ask the CDNs to purge that path. Normal Friday working hours would be fine, thanks! We're going to disable pushing into releases/ until all the issues are sorted, in an attempt to avoid repeated requests for purges.
Content has already been deleted from S3, and CDNs are purging now
Assignee: nobody → jbuckley
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Looks like this needs to be done again since we're trying our 14th build now.
Status: RESOLVED → REOPENED
Flags: needinfo?(jbuckley)
Resolution: FIXED → ---
CDNs are purging now
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Flags: needinfo?(jbuckley)
Resolution: --- → FIXED
Perhaps the delete step was missed ? https://archive.mozilla.org/pub/thunderbird/releases/56.0b4/ exists and has files dated 13-Oct, while the latest candidate is dated 16-Oct in https://archive.mozilla.org/pub/thunderbird/candidates/56.0b4-candidates/build14/.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Argh, sorry everyone, I'm not sure how I messed that up. I have confirmed that I've deleted the files in: /pub/thunderbird/releases/56.0b4/ /pub/thunderbird/candidates/56.0b4-candidates/build14/ and I'm clearing the CDNs now.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
Double Argh. I'm restoring the /pub/thunderbird/candidates/56.0b4-candidates/build14/ directory now, sorry for the misinterpretation!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
:Jorg - Sorry for the trouble, it's still restoring. The S3 API can only do one file at a time (300 left to go). I think it'll be done in 10 minutes, and I'll update this bug when that's done
No problem, thanks for the clarification.
Alright, all files restored & the directory listing is up to date
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
I hit all the main directories and trolled into win32/en-US - all looks good. Thanks Jon
You need to log in before you can comment on or make changes to this bug.