|
|
| (20 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| 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'''."
| | #REDIRECT [[ReleaseEngineering:Buildduty]] |
|
| |
|
| = Duties =
| | '''This page deprecated, please see [[ReleaseEngineering:Buildduty]]''' |
|
| |
|
| * Check the [https://bugzilla.mozilla.org/buglist.cgi?resolution=DUPLICATE;resolution=---;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=%5Bhardware%5D;component=Release%20Engineering;component=Release%20Engineering%3A%20Custom%20Builds;component=Release%20Engineering%3A%20Future;product=mozilla.org 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.
| | Each week there is one person from the Release Engineering team dedicated to helping out developers with releng-related 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 "'''buildduty'''." When nobody is on buildduty (off hours and weekends), consult #build with any issues - in most cases someone is available. |
| * Monitor the following:
| |
| ** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=releng-triage&sharer_id=30066 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 [https://lists.mozilla.org/listinfo/dev-tree-management email] or by [nntp://mozilla.dev.tree-management 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
| |
| ** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=releng-future&sharer_id=30066 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 [https://nagios.mozilla.org/nagios/ 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:
| |
| ** [http://production-master.build.mozilla.org:8010/one_line_per_build?numbuilds=800 p-m]
| |
| ** [http://production-master01.build.mozilla.org:8010/one_line_per_build?numbuilds=800 p-m1]
| |
| ** [http://production-master02.build.mozilla.org:8010/one_line_per_build?numbuilds=800 p-m2]
| |
| ** [http://production-master03.build.mozilla.org:8010/one_line_per_build?numbuilds=800 p-m3]
| |
| ** [http://production-master02.build.mozilla.org:8011/one_line_per_build?numbuilds=800 try build and unittests for win32]
| |
| * Test Masters:
| |
| ** [http://test-master01.build.mozilla.org:8012/one_line_per_build?numbuilds=800 test-master02]
| |
| ** [http://test-master02.build.mozilla.org:8012/one_line_per_build?numbuilds=800 test-master02]
| |
| ** [http://talos-master02.build.mozilla.org:8012/one_line_per_build?numbuilds=800 talos-master02]
| |
| = Schedule = | | = Schedule = |
|
| |
|
| Mozilla Releng Sheriff Schedule ([http://www.google.com/calendar/embed?src=aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com&ctz=America/New_York Google Calendar]|[http://www.google.com/calendar/ical/aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com/public/basic.ics iCal]|[http://www.google.com/calendar/feeds/aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com/public/basic XML]) | | Mozilla Releng Sheriff Schedule ([http://www.google.com/calendar/embed?src=aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com&ctz=America/New_York Google Calendar]|[http://www.google.com/calendar/ical/aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com/public/basic.ics iCal]|[http://www.google.com/calendar/feeds/aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com/public/basic XML]) |
| | = Duties = |
| | Buildduty will: |
| | * Manually kick off runs for try talos builds - file a ticket for this purpose, please |
| | * Keep build slaves humming along nicely |
| | * Monitor #developers irc channel for issues. |
| | * Monitor wait times emails and respond to any unusually long wait times |
| | * Schedule and lead downtimes (if needed) and coordinate with the developers as needed |
| | * Keep [[ReleaseEngineering:Maintenance]] up to date |
| | * Kick self-serve if needed [https://wiki.mozilla.org/ReleaseEngineering/BuildAPI#Kicking Kicking] |
| | * Take any bugs that are "shepherding" bugs requested by A-Team so that they have a point person to get to deployment with |