Changes

Jump to: navigation, search

Sheriffing/How To/Getting started as a sheriff

1,108 bytes added, 16:30, 10 January 2018
added permissions and related actions
* Landing approved patches that are marked as "checkin-needed" onto mozilla-inbound or autoland.
* Backporting approved patches (also called "[[Sheriffing/How_To/Uplifts|uplifting]]") from mozilla-central to one or more of the release stabilization branches (mozilla-beta, mozilla-release, mozilla-esr52, etc) to get the patch into users' hands sooner.
 
== Permissions ==
The following permission have to be set for the mentioned actions:
* commit access level 1 (scm_level_1 LDAP group):
** save job classifications
** retrigger jobs
** push to Try server (test patches, do beta simulations etc.)
** request to add selected jobs to a push
* commit access level 3 (scm_level_3 LDAP group):
** push to mozilla-inbound, mozilla-central etc. (not autoland or modify servo/, see below)
** land patches from within the browser with Review Board ("MozReview")
** request to run job on previous pushes where it might have been skipped ("Backfilling")
* scm_autoland LDAP group:
** push directly to autoland (needed for merges and some backouts)
* scm_servo_vendor LDAP group:
** allow to changes files in the servo/ folder (needed for merges and some backouts)
* vpn_sheriff LDAP group:
** terminate machines running tests
** request to run all missing jobs from menu for a push
** cancel all jobs on non-Try pushes
** manually request Nightlies (?)
* vpn_treestatus LDAP group:
** change the status of the trees (e.g. close on test failures or infrastructure issues)
Confirm
569
edits

Navigation menu