canmove, Confirmed users
2,850
edits
CIDuty: Difference between revisions
Jump to navigation
Jump to search
→What should I take care of?
ChrisCooper (talk | contribs) (→Others) |
ChrisCooper (talk | contribs) |
||
| Line 24: | Line 24: | ||
The [[ReleaseEngineering/Buildduty/Dealing With Outages|Dealing with Outages]] wiki has more instructions. | The [[ReleaseEngineering/Buildduty/Dealing With Outages|Dealing with Outages]] wiki has more instructions. | ||
=== Developer Requests === | |||
Aside from dealing with service outages, responding promptly to developer requests is the most important part of buildduty. | |||
Developer requests will come via bugzilla in the form of new bugs, or may come as “pings” in IRC. Buildduty is expected to be the first point-of-contact for these requests to avoid interrupts to the rest of the team. IRC pings should be translated into bugs once the essence of the request in understood. Bugs should then be triaged into the proper component, and appropriate engineers cc-ed. If the work is actionable by buildduty and the work won't interfere with the completion of other duties, then buildduty should fix the issue. | |||
=== Daily === | === Daily === | ||
| Line 37: | Line 42: | ||
Do the same for bugs in the "All dependencies resolved" section to make sure the next action is taken (re-image, decomm, return to production, etc). | Do the same for bugs in the "All dependencies resolved" section to make sure the next action is taken (re-image, decomm, return to production, etc). | ||
'''Note:''' systemic issues (e.g. test failures that require further investigation) should *not* stay in the buildduty bugzilla component. It may be OK for you to take the bug and work on it depending on how much time you have, but generally these types of bugs should be moved to a more-appropriate component (e.g. General Automation) once buildduty has triaged them. | '''Note:''' systemic issues (e.g. test failures that require further investigation) should *not* stay in the buildduty bugzilla component. It <i>may</i> be OK for you to take the bug and work on it depending on how much time you have, but generally these types of bugs should be moved to a more-appropriate component (e.g. General Automation) once buildduty has triaged them. | ||
Aside from the buildduty report, there may also be [https://nagios.mozilla.org/releng-scl3/cgi-bin/status.cgi?host=all&servicestatustypes=28&hoststatustypes=15&serviceprops=270346&hostprops=270346 unacknowledged nagios alerts] in the #buildduty IRC channel. Deal with them, filing bugs as needed. | Aside from the buildduty report, there may also be [https://nagios.mozilla.org/releng-scl3/cgi-bin/status.cgi?host=all&servicestatustypes=28&hoststatustypes=15&serviceprops=270346&hostprops=270346 unacknowledged nagios alerts] in the #buildduty IRC channel. Deal with them, filing bugs as needed. | ||