Closed
Bug 842990
Opened 13 years ago
Closed 13 years ago
better documentation around dealing with release runner when it fails
Categories
(Release Engineering :: Release Automation, defect)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
(Whiteboard: [shipit])
- Where to find logs
- How to restart release runner
Anything else?
|
Assignee | |
Updated•13 years ago
|
Assignee: nobody → bhearsum
|
|
Assignee | |
Comment 1•13 years ago
|
||
How does https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Troubleshooting#How_to_investigate_release_runner_failures look?
Flags: needinfo?(rail)
|
||
Comment 2•13 years ago
|
||
It looks perfect to me. We could add frequent problems and solutions, but having the docs generic is better - we won't be stupider! :)
Flags: needinfo?(rail)
|
|
Assignee | |
Comment 3•13 years ago
|
||
Aki reminded me that we need docs on what to do when we get the "reconfig exceeded timeout" mail.
|
|
Assignee | |
Comment 4•13 years ago
|
||
Flags: needinfo?(rail)
|
|
Assignee | |
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•