diff options
| author |  Ravi Mistry <rmistry@google.com> | 2017-11-06 16:10:42 -0500 |
|---|---|---|
| committer |  Skia Commit-Bot <skia-commit-bot@chromium.org> | 2017-11-07 01:51:32 +0000 |
| commit | 75a1377e54fb44c84a2712d9c678b1b448a9cffe (patch) | |
| tree | 610bcc302ad8bdebbf2b23694caeb01c1761d036 /site/dev/sheriffing | |
| parent | 7c02cc7934d08da3217ff9a0baae72cb93b09c6b (diff) | |
Add section for how to connect to Skia swarming bots
No-Try: true
Docs-Preview: https://skia.org/?cl=67849
Bug: skia:7098
Change-Id: Ib603bdd2117aab6f626cd68e26529d277a0f1508
Reviewed-on: https://skia-review.googlesource.com/67849
Commit-Queue: Ravi Mistry <rmistry@google.com>
Reviewed-by: Kevin Lubick <kjlubick@google.com>
Reviewed-by: Ben Wagner <benjaminwagner@google.com>
Diffstat (limited to 'site/dev/sheriffing')
| -rw-r--r-- | site/dev/sheriffing/trooper.md | 21 |
1 files changed, 1 insertions, 20 deletions
diff --git a/site/dev/sheriffing/trooper.md b/site/dev/sheriffing/trooper.md index e49d7cfb0e..c21af03e78 100644 --- a/site/dev/sheriffing/trooper.md +++ b/site/dev/sheriffing/trooper.md @@ -49,31 +49,12 @@ Tips for troopers - Install the Skia trooper Chrome extension (available [here](https://chrome.google.com/webstore/a/google.com/detail/alerts-for-skia-troopers/fpljhfiomnfioecagooiekldeolcpief)) to be able to see alerts quickly in the browser. -- Where machines are located: - - Machine name like "skia-gce-NNN", "skia-i-gce-NNN", "ct-gce-NNN", "skia-ct-gce-NNN", "ct-xxx-builder-NNN" -> GCE - - Machine name ends with "a9", "m3" -> Chrome Golo/Labs - - Machine name ends with "m5" -> CT bare-metal bots in Chrome Golo - - Machine name starts with "skia-e-", "skia-i-" (other than "skia-i-gce-NNN"), "skia-rpi-" -> Chapel Hill lab +- See [this section](../testing/swarmingbots#connecting-to-swarming-bots) for details on how to connect to the different Skia bots. - The [chrome-infra hangout](https://goto.google.com/cit-hangout) is useful for questions regarding bots managed by the Chrome Infra team and to get visibility into upstream failures that cause problems for us. -- To log in to a Linux bot in GCE, use `gcloud compute ssh default@<machine - name>`. Choose the zone listed for the - [GCE VM](https://console.cloud.google.com/project/31977622648/compute/instances) - (or specify it using the `--zone` command-line flag). - -- To log in to a Windows bot in GCE, use - [Chrome RDP Extension](https://chrome.google.com/webstore/detail/chrome-rdp/cbkkbcmdlboombapidmoeolnmdacpkch?hl=en-US) - with the - [IP address of the GCE VM](https://console.cloud.google.com/project/31977622648/compute/instances) - shown on the [host info page](https://status.skia.org/hosts) for that bot. The - username is chrome-bot and the password can be found on - [Valentine](https://valentine.corp.google.com/) as "chrome-bot (Win GCE)". - -- To log in to other bots, see the [Skolo maintenance doc](https://docs.google.com/document/d/1zTR1YtrIFBo-fRWgbUgvJNVJ-s_4_sNjTrHIoX2vulo/edit#heading=h.2nq3yd1axg0n) remote access section. - - If there is a problem with a bot in the Chrome Golo or Chrome infra GCE, the best course of action is to [file a bug](https://code.google.com/p/chromium/issues/entry?template=Build%20Infrastructure) |