Sheriffing/Schedule for Tasks performed by Code Sheriffs: Difference between revisions

Jump to navigation Jump to search
updated duties
(add tasks performed by sheriffing lead around merge day)
(updated duties)
Line 1: Line 1:
Version: 4 (Last Updated 2020-02-11)
Version: 5 (Last Updated 2020-06-17)
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 18: Line 18:
||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.
||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.
|- style="vertical-align:top"
|- style="vertical-align:top"
| Land patches and do uplifts to beta || Every 2h
| Land patches || 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.
||Check for patches waiting to land  
|- style="vertical-align:top"
|- style="vertical-align:top"
| Merge integration trees (no central to autoland)|| Mo-Fr every 6h
| Merge autoland tree to mozilla-central || Mo-Fr every 6h
Sa+Su: every 12h
Sa+Su: every 12h
|| Merge autoland to mozilla-central and mozilla-central to autoland if necessary
|| Merge autoland to mozilla-central and mozilla-central to autoland if necessary
|- style="vertical-align:top"
|- style="vertical-align:top"
| central-as-beta simulations || Daily
| central-as-beta simulations || Weekends
||Simulate the code in mozilla-central as mozilla-beta
||Simulate the code in mozilla-central as mozilla-beta
|- style="vertical-align:top"
| beta-as-release simulation || Weekly during the Thursday night shift
||Simulate the code in mozilla-beta as mozilla-release
|- style="vertical-align:top"
|- style="vertical-align:top"
| Clean up list of bugs which don’t get suggested || Weekly
| Clean up list of bugs which don’t get suggested || Weekly
Line 36: Line 33:
# If the bug has been resolved as incomplete, remove it from the document.
# If the bug has been resolved as incomplete, remove it from the document.
# 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.
# 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.
|- style="vertical-align:top"
| 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 [https://github.com/mozilla/probe-scraper 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.
|}
|}


Line 45: Line 39:
|-
|-
! Task !! Schedule !! Details
! Task !! Schedule !! Details
|- style="vertical-align:top"
| central-as-beta simulations || Mon-Fri
||Simulate the code in mozilla-central as mozilla-beta
|- style="vertical-align:top"
| beta-as-release simulation || Thursdays
||Simulate the code in mozilla-beta as mozilla-release
|- style="vertical-align:top"
| 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 [https://github.com/mozilla/probe-scraper 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.
|- style="vertical-align:top"
| beta uplifts || on demand from Release Management
||Check for patches to be uplifted from central to beta. Beta patches shall have landed and build and test coverage before 2am UTC on Mondays, Wednesdays and Fridays when betas are built. Release Management might request to land more on short notice.
|- style="vertical-align:top"
|- style="vertical-align:top"
| Create new beta simulation document|| Monday on which version got increased
| Create new beta simulation document|| Monday on which version got increased
Confirmed users
602

edits

Navigation menu