canmove, Confirmed users
1,126
edits
Sheriffing/Job Visibility Policy: Difference between revisions
Sheriffing/Job Visibility Policy (view source)
Revision as of 16:17, 9 October 2014
, 9 October 2014→3) Runs on mozilla-central and all trees that merge into it: Update list of repos
m (Fix wiki markup) |
(→3) Runs on mozilla-central and all trees that merge into it: Update list of repos) |
||
| Line 25: | Line 25: | ||
=== 3) Runs on mozilla-central and all trees that merge into it === | === 3) Runs on mozilla-central and all trees that merge into it === | ||
* Otherwise job failures when tree X merges into mozilla-central will not be attributable to a single changeset, resulting in either tree closure or backout of the entire merge (see requirement #2). | * Otherwise job failures when tree X merges into mozilla-central will not be attributable to a single changeset, resulting in either tree closure or backout of the entire merge (see requirement #2). | ||
* When filing the release engineering bug to enable your job on all the required trees, ask to enable it on "mozilla-central based trees" and release engineering will enable it in the default config from which all trunk trees inherit (unless the various tree owners have explicitly opted out). As a rough guide, mozilla-central based trees include mozilla-inbound, fx-team, | * When filing the release engineering bug to enable your job on all the required trees, ask to enable it on "mozilla-central based trees" and release engineering will enable it in the default config from which all trunk trees inherit (unless the various tree owners have explicitly opted out). As a rough guide, mozilla-central based trees include mozilla-inbound, fx-team, b2g-inbound as well as many of the other project/disposable repositories. | ||
=== 4) Scheduled on every push === | === 4) Scheduled on every push === | ||