chromium/src
0
Fork 0
Code Activity

Mention branch sheriff label in sheriffing instructions.

Browse Source 
Also fix some lines beyond 80 chars in length.

Bug: 1034648
Change-Id: I58a84218922e8c3d77bac699c2248aa1da9f7195
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2176095
Auto-Submit: Carlos Knippschild <carlosk@chromium.org>
Reviewed-by: Eric Foo <efoo@chromium.org>
Commit-Queue: Carlos Knippschild <carlosk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765075}
This commit is contained in:
Carlos Knippschild
2020-05-04 15:44:58 +00:00
committed by Commit Bot
parent 54e5ba14e7
commit 05c9fd90ce
1 changed files with 17 additions and 7 deletions

24
docs/branch_sheriff.md

@ -56,13 +56,16 @@ Once you've done that, you'll be able to check out branches:
```
To determine the appropriate branch number, you can either use
[chromiumdash](#chromiumdash) or check [milestone.json][milestone-json] directly.
[chromiumdash](#chromiumdash) or check [milestone.json][milestone-json]
directly.
### Findit
As FindIt is not available on branches, one way to try to find culprits is using
`git bisect` locally and upload changes to a gerrit CL and run the needed trybots
to check. This is especially useful when the errors are not reproducible on your
local builds or you don't have the required hardware to build the failed tests.
`git bisect` locally and upload changes to a gerrit CL and run the needed
trybots to check. This is especially useful when the errors are not reproducible
on your local builds or you don't have the required hardware to build the failed
tests.
### Flaky tests
@ -81,15 +84,22 @@ relevant release TPM as listed on [chromiumdash][chromiumdash-schedule].
### Sheriff-o-Matic
Use the [branch SoM console][sheriff-o-matic] rather than the main chromium console.
Use the [branch SoM console][sheriff-o-matic] rather than the main chromium
console.
### Consoles
Use the [beta][main-beta] and [stable][main-stable] branch consoles rather than the
main console. A new console is created for each milestone. They are named
Use the [beta][main-beta] and [stable][main-stable] branch consoles rather than
the main console. A new console is created for each milestone. They are named
"Chromium M## Console" and can be found under the
[Chromium Project](https://ci.chromium.org/p/chromium).
### Monorail issues (crbug)
Refer and use the
[Sheriff-Chrome-Release label](https://bugs.chromium.org/p/chromium/issues/list?q=label%3ASheriff-Chrome-Release)
to find and tag issues that are of importance to Branch sheriffs.
### Chromiumdash
[chromiumdash][chromiumdash] can help you determine the branch number for a