canmove, Confirmed users
2,850
edits
CIDuty: Difference between revisions
Jump to navigation
Jump to search
→Daily
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) (→Daily) |
||
| Line 25: | Line 25: | ||
=== Daily === | === Daily === | ||
==== Triage ==== | ==== Triage ==== | ||
The [https://secure.pub.build.mozilla.org/builddata/reports/slave_health/buildduty_report.html Buildduty report] (generated hourly) should be your starting point for triage. | |||
At the top, it lists unassigned bugs for loan requests. You should try to keep this queue empty to make sure developers are unblocked. The wiki has [[ReleaseEngineering/How_To/Loan_a_Slave|instructions for how to loan a slave]]. | |||
After loans are taken care of, make sure that bugs in the "No dependencies" section get dependencies filed, e.g. diagnosis bug, decomm bug, 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 productionetc). Use the "View list in bugzilla" links to navigate the bugs more easily. | |||
'''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. | |||
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. | |||
|} | |} | ||
==== Pending Jobs ==== | ==== Pending Jobs ==== | ||
We will sometimes be starved for capacity on one or more platforms. Because there are multiple potential causes, and hence multiple possible paths to resolution, the steps for [[ReleaseEngineering/How_To/Dealing_with_high_pending_counts|dealing with high pending counts]] are on their own page. | We will sometimes be starved for capacity on one or more platforms. Because there are multiple potential causes, and hence multiple possible paths to resolution, the steps for [[ReleaseEngineering/How_To/Dealing_with_high_pending_counts|dealing with high pending counts]] are on their own page. | ||