canmove, Confirmed users
1,126
edits
Sheriffing/Job Visibility Policy: Difference between revisions
Jump to navigation
Jump to search
→4) Runs on every push: Explicitly mention coalescing and PGO runs
(Add "Requesting changes in visibility" section) |
(→4) Runs on every push: Explicitly mention coalescing and PGO runs) |
||
| Line 22: | Line 22: | ||
* 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). | ||
=== 4) | === 4) Scheduled on every push === | ||
* Otherwise job failures will not be attributable to a single changeset, resulting in either tree closure or backout of multiple pushes (see requirement #2). | * Otherwise job failures will not be attributable to a single changeset, resulting in either tree closure or backout of multiple pushes (see requirement #2). | ||
* An exception is made for nightly builds with an virtually equivalent non-nightly variant that is built on every push. | * An exception is made for nightly builds with an virtually equivalent non-nightly variant that is built on every push & for tests run on PGO builds. | ||
* Note also that coalescing (buildbot queue collapsing when there is more than one queued job) may mean that not all scheduled jobs actually get run. Whilst coalescing makes sheriffing harder, it's a necessary evil given that automation infrastructure demand frequently outstrips supply. | |||
=== 5) Easily run on try server === | === 5) Easily run on try server === | ||