Sheriffing/Schedule for Tasks performed by Code Sheriffs

From MozillaWiki
Jump to: navigation, search

Version: 4 (Last Updated 2020-02-11)

Task Schedule Details
Watch trees Always Watch the following trees for failures, classify them, do backouts and escalate infra issues:
  • trunk (mozilla-central, autoland)
  • mozilla-beta
  • mozilla-release
  • mozilla-esr trees (all of them which are available in Treeherder; often there is only 1, but for some time 2 when their cycles overlap)

Open them up to the oldest push with unclassified failures (excluding backfills and retriggers added >4h after the push) or running jobs.

Email reading Start of shift, every 30 minutes Help other people by answering needinfo requests etc.
Read new, not suggested bugs Start of shift Get used to new frequent failures created since the last shift and which Treeherder doesn’t suggest. These are added at the top and further down.
Land patches and do uplifts to beta Every 2h Check for patches waiting to land (have keyword “checkin-needed” at Bugzilla) or to be uplifted from central to beta. Beta patches shall have landed and build and test coverage before 9am Pacific Time on Mondays and Thursdays when betas are built. Release Management might request to land more on short notice.
Merge integration trees (no central to autoland) Mo-Fr every 6h

Sa+Su: every 12h

Merge autoland to mozilla-central and mozilla-central to autoland if necessary
central-as-beta simulations Daily Simulate the code in mozilla-central as mozilla-beta
beta-as-release simulation Weekly during the Thursday night shift Simulate the code in mozilla-beta as mozilla-release
Clean up list of bugs which don’t get suggested Weekly Check if bugs are still active or needed for beta. Preferable on the weekend when there is more time for this.
  1. Open the Bugzilla links from the document.
  2. If the bug has been resolved as incomplete, remove it from the document.
  3. If it is resolved fixed but the widget showing the number of classifications per day still shows activity, it is used for non-trunk trees (e.g. beta, release, esrs). Keep it in that case.
version increase simulation Second Tuesday after version increase The first time a version increase simulations is done is the second Tuesday after the version number got increased (to let probe-scraper alert for expiring probes before and reduced the failures in the version increase simulation), later as needed - at least a week before the next version increase to verify fixes worked and no new issues have been added.

Simulate the code in mozilla-central with the next higher version number.

Sheriffing and quality/stability related tasks executed by one person (Aryx)

Task Schedule Details
Create new beta simulation document Monday on which version got increased Clone the current beta simulation document, adjust versions and dates and send it to code sheriffs and release management.
Request new version to be added to Bugzilla Monday before next version increase The Gecko and Firefox version will get increased and bugs cannot be set as fixed in the new version with the Bugherder tool until the version got added to The new version gets requested one week in advance to allow easier coordination with the Bugzilla team.

Example bug

  1. Clone the bug which added the latest version to Bugzilla.
Add new version to tree statistics Monday on which version got increased Tool which shows how often and how long the trees got closed
Last cycle quality metrics Monday on which version got increased Accumulate weekly quality metrics for last release cycle
New Nightly respin statistics Monday on which version got increased Set up new sheet to track backouts from mozilla-central and Nightly respins