ReleaseEngineering/Sheriffing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Redirected page to ReleaseEngineering:Buildduty)
 
(32 intermediate revisions by 6 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.
#REDIRECT [[ReleaseEngineering:Buildduty]]


= Duties =
'''This page deprecated, please see [[ReleaseEngineering:Buildduty]]'''


* Monitor the following:
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.
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=release-eng-triage&sharer_id=20203 release-eng-triage] bug queue.  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)
* Update the latest "Buildslave reboots" 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).
* Triage incoming RelEng bugs in the [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=releng-triage&sharer_id=30066 triage queue]
 
*Helpful links:
** Suggested views to see problems in builds [http://production-master.build.mozilla.org:8010/one_line_per_build?numbuilds=800 p-m1] and [http://production-master02.build.mozilla.org:8010/one_line_per_build?numbuilds=800 p-m2].


= 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 =
= Schedule (historical) =
Buildduty will:
{| class="fullwidth-table"
* Manually kick off runs for try talos builds - file a ticket for this purpose, please
| '''Week'''
* Keep build slaves humming along nicely
| '''Person'''
* Monitor #developers irc channel for issues.
| '''Notes'''
* 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
| September 14, 2009 - September 18, 2009
* Keep [[ReleaseEngineering:Maintenance]] up to date
| Chris Cooper (coop), Armen Zambrano (armenzg)
* 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
|-
| September 8, 2009 - September 11, 2009 (Labour Day Monday is a holiday for US & Canada)
| Aki Sasaki, John Ford (aki, jhford)
|
|-
| August 31, 2009 - September 4, 2009 (PDT)
| Lukas Blakk (lsblakk)
|
|-
| August 25, 2009 - August 29, 2009 (PDT)
| Lukas Blakk (lsblakk)
|
|-
| August 17, 2009 - August 21, 2009 (PDT)
| Alice Nodelman and Armen Zambrano (alice, armenzg)
|
|-
| August 11, 2009 - August 16, 2009 (PDT)
| Alice Nodelman (alice)
|
|-
| August 3, 2009 - August 8, 2009 (EDT)
| Chris Cooper (coop)
|
|-
| July 27, 2009 - July 31 (EDT)
| Ben Hearsum (bhearsum)
|
|-
| July 20, 2009 - July 24, 2009 (EDT)
| Chris AtLee (catlee)
|
|-
| July 13, 2009 - July 17, 2009 (PDT)
| Aki Sasaki (aki)
| [[ReleaseEngineering:Sheriffing:Notes:2009-07-13 | Notes]]
|-
| July 06, 2009 - July 10, 2009 (EST)
| Ben Hearsum (bhearsum)
| [[ReleaseEngineering:Sheriffing:Notes:2009-07-06 | Notes]]
|-
| June 29, 2009 - July 4, 2009 (EST)
| Armen Zambrano Gasparnian, Chris Cooper (armenzg, coop)
| [[ReleaseEngineering:Sheriffing:Notes:2009-06-29 | Notes]]
|-
| June 22, 2009 - June 26, 2009 (EST)
| Armen Zambrano Gasparnian, Chris Cooper (armenzg, coop)
| [[ReleaseEngineering:Sheriffing:Notes:2009-06-22 | Notes]]
|-
| June 15, 2009 - June 19, 2009 (PST)
| Lukas Blakk (lsblakk)
| [[ReleaseEngineering:Sheriffing:Notes:2009-06-15 | Notes]]
|-
| June 7, 2009 - June 11, 2009 (EST)
| Lukas Blakk (lsblakk)
| [[ReleaseEngineering:Sheriffing:Notes:2009-06-07 | Notes]]
|-
| June 1, 2009 - June 5, 2009
| Alice Nodelman, Lukas Blakk (alice, lsblakk)
| [[ReleaseEngineering:Sheriffing:Notes:2009-06-01 | Notes]]
|-
| May 29, 2009 (EDT)
| Chris AtLee (catlee)
|
|-
| May 24, 2009 - May 28, 2009 (Pacific time, M-F NZ)
| Nick Thomas (nthomas)
| [[ReleaseEngineering:Sheriffing:Notes:2009-05-24 | Notes]]
|-
| May 18, 2009 - May 22, 2009
| Aki Sasaki (aki)
| [[ReleaseEngineering:Sheriffing:Notes:2009-05-18 | Notes]]
|-
| May 11, 2009 - May 15, 2009
| Ben Hearsum (bhearsum)
| [[ReleaseEngineering:Sheriffing:Notes:2009-05-11 | Notes]]
|-
| May 4, 2009 - May 8, 2009
| Chris Cooper (coop)
| [[ReleaseEngineering:Sheriffing:Notes:2009-05-04 | Notes]]
|-
| Apr 27 - May 1, 2009
| Alice Nodelman (alice)
| [[ReleaseEngineering:Sheriffing:Notes:2009-04-27 | Notes]]
|-
| Apr 17, Apr 20 - Apr 24, 2009
| Chris AtLee (catlee)
| [[ReleaseEngineering:Sheriffing:Notes:2009-04-20 | Notes]]
|-
| Apr 13 - Apr 16, 2009
| John O'Duinn (joduinn)
| [[ReleaseEngineering:Sheriffing:Notes:2009-04-13 | Notes]]
|-
| Apr 6 - Apr 10, 2009
| Aki Sasaki (aki)
| [[ReleaseEngineering:Sheriffing:Notes:2009-04-06 | Notes]]
|-
| Mar 30 - Apr 3, 2009
| Alice Nodelman (alice)
| [[ReleaseEngineering:Sheriffing:Notes:2009-03-30 | Notes]]
|-
| Mar 22 - 26, 2009 (Pacific time)
| Nick Thomas (nthomas)
| [[ReleaseEngineering:Sheriffing:Notes:2009-03-23 | Notes]]
|-
| Mar 16 - 20, 2009
| Ben Hearsum (bhearsum)
| [[ReleaseEngineering:Sheriffing:Notes:2009-03-16 | Notes]]
|-
| Mar 9 - 13, 2009
| Chris Cooper (coop)
| [[ReleaseEngineering:Sheriffing:Notes2009Mar09-13|Notes]]
|-
| Mar 2 - 6, 2009
| Aki Sasaki (aki)
|
|-
| Feb 23 - 27, 2009
| Ben Hearsum (bhearsum)
|
|-
| Feb 17 - Feb 20, 2009
| Chris AtLee (catlee)
|
|}
 
(new entries at the top)
(hopefully we can get this moved onto the sheriff's calendar)

Latest revision as of 17:09, 4 October 2011

Redirect to:

This page deprecated, please see ReleaseEngineering:Buildduty

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.

Schedule

Mozilla Releng Sheriff Schedule (Google Calendar|iCal|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 Kicking
  • Take any bugs that are "shepherding" bugs requested by A-Team so that they have a point person to get to deployment with
Retrieved from "https://wiki.allizom.org/index.php?title=ReleaseEngineering/Sheriffing&oldid=354697"