Closed Bug 1159226 Opened 9 years ago Closed 8 years ago

When we go for a build2, automation should take care care of purging CDNs

Categories

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

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: massimo, Unassigned)

References

Details

During the release of Firefox 38.0b8, we hit bug 1159060;

When we start a build2 (or any successive build), automation should take care of cleaning up the previous builds (if it's not already done) and start the CDNs purge process. Even just filing the CDNs bug would be a good starting point; if we can automate the purging, it would be even better.
Given how infrequently CDN purges actually work, is this worth it? Maybe we should invest the effort into reworking to make them unnecessary...
I'm inclined to agree with Ben, and bug 1159804 covers that situation. Any objections to going that route instead ?
I'd be all for that. ;-)
Let's wontfix this for 2 reason:
1) doesn't happen too offen
2) deleting files is dangerous
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.