ReleaseEngineering/Sheriffing

Each week there will be one person from the Release Engineering team dedicated to helping out developers with build / unittest / talos issues. This person will be available during his or her regular work hours for the whole week. This is similar to the sheriff role that rotates through the developer community. To avoid confusion, the releng sheriff position is informally known as "build duty."

Duties

For information on to perform many of these duties, see ReleaseEngineering:Sheriffing:HowTo

• Manually kick off runs for try talos builds as per HowTo (People should be filing bugs to request talos runs - check the tryrequest buzilla tag) -- Direct people to http://mzl.la/tryhelp for self-serve doc
• Check the hardware buzilla tag and if there are new slaves/moved slaves bugs needing to be worked on, get the slaves into/back into the appropriate pool.
• Check the buildduty tag to see known problems (it might also show items from the "hardware" tag)
• Monitor the following:
  • releng-triage bug queue. Triage incoming RelEng bugs, ask in #mozbuild to see if anybody wants to take it on, otherwise move it to Future, or bring it up at the next team meeting.
  • #developers irc channel for issues. Make sure the sheriff knows who you are, and that they can contact you if they have any questions or issues.
  • dev.tree-management newsgroup (by email or by nntp)
  • wait times emails and respond to any unusually long wait times (hopefully with a reason)
  • tag any bugs that the next person on buildduty should be aware of with [buildduty] in the whiteboard field
  • releng-future bug queue. As time allows, try to knock down as many bugs from the future queue as possible. A good strategy is to start with bugs that have not been modified in the longest time.
• Update the latest "Buildslave reboots" bug with machines that need a reboot. Look in the nagios page in the "Service details"->"All problems"(on the "Service Status Totals" table).
• Schedule and lead downtimes (if needed) and coordinate with the developers as needed
  • Keep ReleaseEngineering:Maintenance up to date
  • Create an "Unscheduled downtime tracking bug" and put the link in the #mozbuild topic for the week's downtime bug gathering. Use the alias "releng-downtime" to make it easy to find:
    • https://bugzilla.mozilla.org/show_bug.cgi?id=releng-downtime

• Follow up on builds (one line per build):
  • p-m1 - builders
  • p-m2 - mobile
  • p-m3 - builders
  • try build and unittests for win32
  • bm1:8010
  • bm2:8010
• Test Masters:
  • tm01
  • tm02
  • talos-m02
  • bm1:8011
  • bm1:8012
  • bm2:8011
  • bm2:8012
• Where all slaves are connected to:

pm	pm01	pm02:8010	pm02:8011	pm03	tm02	tm01	tm02'
bm1:8010	bm1:8011	bm1:8012	bm2:8010	bm2:8011	bm2:8012

Schedule

Mozilla Releng Sheriff Schedule (Google Calendar|iCal|XML)