Closed
Bug 602026
Opened 14 years ago
Closed 12 years ago
Improve error/retry handling in release scripts that do downloading
Categories
(Release Engineering :: Release Automation: Other, defect, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Unassigned)
Details
(Whiteboard: [automation][releases])
In the updates (both regular and MU) generation scripts a download failure kills the automation. It would be useful to go through any scripts that do downloading and add handling for failure, clean up, and retry the download a couple of times in case the error is just network failure and not actually the absence of the file (this happened to me twice in 3.5.14)
Updated•14 years ago
|
Status: NEW → ASSIGNED
Updated•13 years ago
|
Blocks: hg-automation
Updated•12 years ago
|
No longer blocks: hg-automation
Comment 1•12 years ago
|
||
Mass move of bugs to Release Automation component.
Blocks: hg-automation
Component: Release Engineering → Release Engineering: Automation (Release Automation)
Updated•12 years ago
|
No longer blocks: hg-automation
Comment 2•12 years ago
|
||
I'm pretty sure we're retrying everywhere we can now. The specific example of updates noted in comment #0 isn't an issue anymore, because we did that work at build time (and retry the downloads).
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•