Closed Bug 683415 Opened 13 years ago Closed 13 years ago

Optimisations for release automation

Categories

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

x86
All
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: nthomas, Unassigned)

Details

In the updates step we eventually get to - create partials and fix up perms - upload partials - upload test snippets - backupsnip for test snippets - pushsnip for test snippets - upload release snippets - upload beta snippets (if applicable) - compare release to releasetest - wait 5 minutes for NFS cache to clear - send email to r-d - dependent builders start * update verify builders * check permissions * antivirus We can re-order this to remove dead-times when automation/QA could be doing things: - create partials and fix up perms - upload partials - upload test snippets - backupsnip for test snippets - pushsnip for test snippets - wait for 2 minutes for NFS cache to clear - send email to r-d - trigger builders * check permissions * antivirus - upload release snippets - upload beta snippets (if applicable) - compare release to releasetest - trigger builders * update verify builders
Priority: -- → P3
found in triage.
Component: Release Engineering → Release Engineering: Automation
QA Contact: release → catlee
Bulk move of bugs to Release Automation component.
Component: Release Engineering: Automation (General) → Release Engineering: Automation (Release Automation)
Mass move of bugs to Release Automation component.
No longer blocks: hg-automation
Is this still relevant in the partials-at-build-time world?
For 12.0b1 there was an 11 minute delay between end of the pushsnip and the updates job finishing. Maybe a bit more if you consider only first half or so of pushsnip is useful right now, but that'll change when we finally switch to PHX. --> WONTFIX
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.