cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 15:43:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Moved LUCI content to https://go.dev/wiki/LUCI

Michael Pratt 2023-10-05 15:11:22 -04:00
parent 2ae6969c9a
commit 2879b54768
1 changed files with 1 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
GerritAccess.md

@ -11,23 +11,7 @@ TryBots run in a somewhat-secure and somewhat-isolated environment,
but they're not perfectly security hardened.
You must skim the CL for anything malicious before starting TryBots.
Voting Commit-Queue+1 asks CQ to run the CL on the TryBots.
When the TryBots finish, CQ will reply with results,
voting either TryBot-Result+1 (pass) or TryBot-Result-1 (fail).
Important results (e.g. failures) will also appear as chips at the top
of the Gerrit page for the CL, under the commit message.
![A red box indicating the location of the checks under the commit
message on the Gerrit page for an example CL.](https://github.com/golang/go/assets/1248668/93267ff3-11cd-41f7-b268-a5cc342cfcd3)
More details about what was run are available at the "Checks" tab
on the Gerrit CL page.
![A red arrow pointing to the location of the checks tab on the
Gerrit page for an example CL.](https://github.com/golang/go/assets/1248668/1a11fa8c-14cd-4b97-968c-6c52a8634c51)
Every TryBot run includes a default set of the most common builders.
[SlowBots](https://go.dev/wiki/SlowBots) provide additional testing controls.
See [LUCI](https://go.dev/wiki/LUCI#TryBots) for details on triggering TryBots.
All approvers (see next section) have TryBot access automatically. Others can request TryBot access. See [Requesting Access](#requesting-access) below.