Sheriffing/Schedule for Tasks performed by Code Sheriffs
Version: 1 (Last Updated 2018-08-21)
| Task | Schedule | Details |
|---|---|---|
| Watch trees | Always | Watch the following trees for failures, classify them, do backouts and escalate infra issues:
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 | Mo-Fr every 6h
Sa+Su: every 12h |
Merge autoland and mozilla-inbound to mozilla-central and back |
| Beta simulations | Daily | Simulate the code in mozilla-central as mozilla-beta |
| Merge mozilla-central to mozilla-beta | Daily if late in release cycle | After beta simulations without any existing perma failures, merge mozilla-central to mozilla-beta. Use the revisions from the beta simulations.
See dates in beta simulation document when this has to be done. |
| 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.
|