canmove, Confirmed users
2,850
edits
CIDuty: Difference between revisions
Jump to navigation
Jump to search
→Buildduty Triage
ChrisCooper (talk | contribs) (→Weekly) |
ChrisCooper (talk | contribs) |
||
| Line 31: | Line 31: | ||
=== Daily === | === Daily === | ||
==== Buildduty Triage ==== | ==== Buildduty Bug 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. | 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. | ||
| Line 38: | Line 38: | ||
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]]. | 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. | 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. The specific next steps will depend on the issue: [https://wiki.mozilla.org/Category:Release_Engineering_How_To Release Engineering How-Tos]. | ||
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). Again, the specific next steps will depend on the issue: [https://wiki.mozilla.org/Category:Release_Engineering_How_To Release Engineering How-Tos]. | ||
'''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. | '''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. | ==== Alerts ==== | ||
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] or SNS alerts from [https://papertrailapp.com/dashboard papertrail] in the #buildduty IRC channel. Deal with them, filing bugs as needed: [https://wiki.mozilla.org/Category:Release_Engineering_How_To Release Engineering How-Tos]. | |||
==== Infrastructure performance ==== | ==== Infrastructure performance ==== | ||