DashboardBuilders, SlowBots: remove documentation for legacy builders The legacy builders have been fully stopped and don't work anymore. The documentation for them is obsolete and misleading. Remove it. For golang/go#67761. Change-Id: I71d3568d7dfee2cd24012c4a03dd955cc2df8359 Reviewed-on: https://go-review.googlesource.com/c/wiki/+/796382 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
diff --git a/DashboardBuilders.md b/DashboardBuilders.md index 945ee49..a516142 100644 --- a/DashboardBuilders.md +++ b/DashboardBuilders.md
@@ -56,19 +56,3 @@ Generally, low-capacity builders only run code that's already been reviewed & submitted (post-submit testing). We only enable pre-submit testing for builders run by the Go team that have a lot of hardware available. However, the [Gomote tool](/wiki/Gomote) is available for a number of people on the Go team and in the Go community that lets them have arbitrary access to the builders for development & debugging. For paranoia reasons, you might want to run your builder in an isolated network that can't access any of your internal resources. - -## Coordinator Builders (legacy) - -This section describes the custom testing solution used previously by the Go project, prior to the migration to LUCI. - -Build configs (at the top) and host configs (bottom) are listed here: - -https://farmer.golang.org/builders - -A builder runs on a certain host type. (e.g. `linux-386-387` is a build type. It runs on `host-linux-kubestd`, a Kubernetes-based linux/amd64 host) - -They come from the file https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go - -For design details about the coordinator, see https://go.dev/s/builderplan - -Information about builder machines, how many are running and their status can be found at https://farmer.golang.org/
diff --git a/SlowBots.md b/SlowBots.md index 1d9d9fe..14e0b07 100644 --- a/SlowBots.md +++ b/SlowBots.md
@@ -60,38 +60,3 @@ - If you're running SlowBots for a CL for the main Go repository, then every build that matches the branch the CL is for will work. For example, if you have a CL for the `master` branch, then every build with a name containing `gotip` will work as expected (`x_tools-gotip-linux-amd64`, `gotip-windows-amd64`, etc.). If you have a CL for the `release-branch.go1.21` branch, then every build with a name containing `go1.21` will work as expected (`x_tools-go1.21-linux-amd64`, `go1.21-windows-amd64`, etc.). TODO: Apply these guidelines as filters automatically. - -### Pre-LUCI SlowBots - -We're currently in the middle of a migration to a new open-source CI system created by the Chromium project called LUCI. The above instructions describe how to run SlowBots on LUCI, but not all ports have been migrated to LUCI yet. In the interim, these ports are still available on the old infrastructure. Below are instructions on how to use SlowBots on the old infrastructure. - -- Use the Gerrit web UI to reply and select `Run-TryBot` = `+1` instead of `Commit-Queue` = `+1`. -- **Before clicking "Send"** write a magic comment in the comment section (where it says _Say something nice..._): - -``` -TRY=ppc64le, freebsd, netbsd-386, ios, linux-arm64-packet -``` - -... where the terms after `TRY=` are either: - -- `GOOS` (picks best one) -- `GOARCH` (picks best one) -- `GOOS-GOARCH` (picks best one) -- `specific-builder-name` (you specify it explicitly by its exact name; see the full list at https://farmer.golang.org/builders) - -For the main Go repository, the terms after `TRY=` can also be: - -- `x/repo`, where `repo` is one of the golang.org/x repositories whose tests should be executed. This runs a default builder for the given repo (`linux-amd64` as of writing). -- `x/repo@builder`, where `repo` is as above, and `builder` is a builder name from the [builder list](https://farmer.golang.org/builders). This runs the specified builder for the given repo. For example, `x/sys@linux-arm64-aws`. - -When running TryBots again later, the most recent `TRY=` comment on the current patchset is used. To turn it off set `TRY=` with an empty string after the equals sign. If the current patchset doesn't have a `TRY=` comment, the most recent `TRY=` comment is used. - -#### Pitfalls with Pre-LUCI SlowBots - -- `TRY=` comments are ignored if they're not on the same comment that started the TryBots -- TryBots (and SlowBots) don't run if there's already a TryBot-Result -- The `git-codereview mail` tool's `-trybot` flag doesn't support this yet, so use the web UI. -- If TryBots are already running, deleting the `Run-TryBot+1` vote and re-doing it won't re-start the TryBot set, so it won't look at your TRY= line, until the next run when it's done. (But you'll need to delete the TryBot-Result somehow: manually, rebasing, uploading new version) -- If you select a builder that's offline, it'll currently just wait forever for it to show up. There's no timeout yet. -- If you specify an unknown `TRY=` token, it'll just ignore it and won't report an error. -- There's no `all` alias. That's kinda intentional, to prevent overuse that might cause the SlowBots to get even slower for everybody. But we might add it later anyway. See [golang.org/issue/34501#issuecomment-544585711](https://go.dev/issue/34501#issuecomment-544585711).