Remove all references to the benchmark, as it no longer exists
diff --git a/docs/bazel-monitoring.md b/docs/bazel-monitoring.md
index ffec429..f6d3654 100644
--- a/docs/bazel-monitoring.md
+++ b/docs/bazel-monitoring.md
@@ -17,7 +17,6 @@
- [bazel-slow-tests](https://ci.bazel.io/job/bazel-slow-tests)
- [bazel-remote-tests](https://ci.bazel.io/job/bazel-remote-tests)
- [Tutorial](https://ci.bazel.io/job/Tutorial)
- - [benchmark](https://ci.bazel.io/job/benchmark)
- [nightly](https://ci.bazel.io/job/bazel/job/nightly)
- [release](https://ci.bazel.io/job/bazel/job/release)
@@ -45,7 +44,6 @@
The build sheriff should monitor the outputs of these types of jobs:
* [global tests](user.md#global-jobs)
-* benchmark
* [postsubmits](user.md#postsubmit)
## Global tests
@@ -71,17 +69,6 @@
2. add the "breakage" label to the bug
3. add the "release blocker" label if the breakage is on the release job
-## Benchmark
-
-URL: https://ci.bazel.io/job/benchmark
-
-How to investigate: look at the output logs:
-
-* if the job fails with a java error or build error: [file a bug to
- bazelbuild/bazel](https://github.com/bazelbuild/bazel/issues/new)
-* otherwise: [file a bug to
- bazelbuild/continuous-integration](https://github.com/bazelbuild/bazel/continuous-integration/new)
-
## Postsubmits
These are all the other monitored jobs.
diff --git a/docs/jobs.md b/docs/jobs.md
index d4fa119..79ea9e4 100644
--- a/docs/jobs.md
+++ b/docs/jobs.md
@@ -11,10 +11,6 @@
Several jobs control the bootstrap and maintenance of Bazel, they
are mostly under the `maintenance` and `bazel` folders:
-* `benchmark`: benchmarks Bazel performance
-
- This job runs continuously and publishes results at https://perf.bazel.build
-
* `maintenance/install-bazel`: installs Bazel release on all workers
* `maintenance/gerrit-verifier`: detects pending reviews on Gerrit that
need validation.
diff --git a/docs/user.md b/docs/user.md
index 3d4433d..388ed93 100644
--- a/docs/user.md
+++ b/docs/user.md
@@ -10,7 +10,6 @@
* runs presubmit tests (on a pending change)
* runs postsubmit tests (on the master branch)
* handles the release project of Bazel
-* handles performance benchmarks
If you wish to add or modify a configuration for one of the projects on
Bazel CI, see the [project owner documentation](owner.md).
@@ -145,13 +144,3 @@
In addition to testing all the jobs, the [Global test](#global-tests) handles
pushing artifacts that are created by a release branch to GCS and to the GitHub
release system.
-
-## Performance benchmarks
-
-Performance benchmarks run once a day.
-
-This job runs performance tests for each new commit since the previous
-benchmarking run, thus each commit is benchmarked individually.
-
-The job publishes a report for each commit, you can find these at
-[perf.bazel.build](https://perf.bazel.build).
diff --git a/gce/vm.sh b/gce/vm.sh
index 3c6ef17..6ef0736 100755
--- a/gce/vm.sh
+++ b/gce/vm.sh
@@ -68,8 +68,6 @@
"windows-slave-2 windows-server-2012-r2-dc-v20160112-vs2015-cpp-python-msys windows-x86_64-2 europe-west1-d default windows-startup-script-ps1=jenkins-slave-windows.ps1"
"windows-slave-3 windows-server-2012-r2-dc-v20160112-vs2015-cpp-python-msys windows-x86_64-3 europe-west1-d default windows-startup-script-ps1=jenkins-slave-windows.ps1"
"windows-slave-4 windows-server-2012-r2-dc-v20160112-vs2015-cpp-python-msys windows-x86_64-4 europe-west1-d default windows-startup-script-ps1=jenkins-slave-windows.ps1"
- # For benchmark
- "ubuntu-16-04-benchmark-slave ubuntu-1604-lts ubuntu_16.04-x86_64-benchmark-1 europe-west1-d default startup-script=jenkins-slave.sh ubuntu-16-04-slave.sh bootstrap-bazel.sh linux-android.sh cleanup-install.sh"
)
# Jenkins controller for ci.bazel.io
