Most services in the Rust Infrastructure are deployed via
rust-central-station. Questions about infrastructure, including current
status, should go to the #t-infra Zulip stream.
Our stability guarantees: many of our services rely on publicly-accessible
storage and APIs, but not all of these are intended for public consumption. At
the moment, only the resources behind , meaning that those resources will not change without (at least) prior
notice. If you are relying on other parts of the Rust project infrastructure for
your own work, please let the infrastructure team know.
static.rust-lang.org are considered
Rust Log Analyzer
analyzes CI build logs to extract error messages and posts them to the pull
request. It is run by TimNN.
Homu is a bot which manages pull
requests. It is often referred to as “bors” due to the name of its
bot user account.
Approved pull requests are placed in
a queue from which tests are
Documentation on homu commands can be found
Alex Crichton if something
goes wrong with the bot.
rfcbot is a bot
( bot user account) which helps manage async
decision making on issues and PRs (typically RFCs). Team members can view any
pending requests for review on the FCP dashboard.
Documentation on rfcbot commands can be found
in the rfcbot repository.
rustbot is a bot ( bot user
account) to assist with managing issues and PRs
to allow users to label and assign without GitHub permissions. See
triagebot for more information.
DXR is a cross-referenced source index
for Rust, allowing the Rust source tree to be navigated and searched with ease.
It is generated by rust-dxr
perf offers information
about the performance of
rustc over time, and a bot for on-demand benchmarking.
It is split into a data
collector and a web frontend + bot. The raw performance
data is available here
and can be browsed on the perf website.
One-off performance runs can done by addressing the
( bot user account). You can trigger the
necessary try-build and queue a perf run by saying
@bors try @rust-timer queue
(Technically, the requirement is that the
queue command finishes executing prior
to the try build completing successfully.)
for further bot commands.
Rust Playground allows you
to experiment with Rust before you install it locally, or in any other case
where you might not have the compiler available. The Rust playground can be
Crater is a tool to run
experiments across the whole Rust ecosystem. Its primary purpose is to detect
regressions in the Rust compiler, and it does this by building large number of
crates, running their test suites and comparing the results between two
versions of the Rust compiler.
Crates comes with a
bot to trigger experiments.
docs.rs builds and serves the rustdoc documentation for
all crates on crates.io. Issues may be filed on the docs.rs
repository. See the #docs-rs channel on
Discord for discussion or urgent issues.
The state of tools included with Rust are tracked on the
page. When each PR is
merged via CI, the status of each tool is recorded in a JSON file and stored
in the toolstate repo.
For further information, see the toolstate system documentation.
history tracks the
status of every rustup component for every platform over time. See the
repository for more
Tracker tracks and
compares how long CI jobs take over time. It is run by Alex
Highfive is a bot
( bot user account) which was previously
used to welcome newcomers and assigned reviewers. This service has been
replaced with rustbot.