CI Runners are machines that run an agent process, registering themselves with the CI platform. The CI platform documentation refers to them as “Self-hosted Runners.” These machines run the Bazel command-line, so the Bazel JVM server also runs on them. Since Bazel stores cache in memory, a JVM restart incurs a performance penalty.Documentation Index
Fetch the complete documentation index at: https://docs.aspect.build/llms.txt
Use this file to discover all available pages before exploring further.
- The runners form an elastic pool of machines with an auto-scaler that interfaces with the CI provider.
- These CI Runners are persistent, accepting more CI jobs until they scale down.
- When a new machine boots, you can optionally
warmit with on-disk caches. This avoids repository rule fetching, extraction, and setup. - Performance optimizations include a RAID0 array over multiple solid-state disks for maximum filesystem Input/Output Operations Per Second.

