Update infrastructure page#244
Merged
Merged
Conversation
This adds some further documentation about the rust infrastructure based on the description of the different projects in their respective documentation. Additionally it also removes the dead links to the outdated buildbot (buildbot.rust-lang.org) and the crater overview which does not exist in this form (crater.rust-lang.org). Responsible maintainers to the different projects has not been added or altered to prevent mistakes, since I'm not familiar with the internal responsibilities of the involved parties. The `https://rusty-dash.com/fcp` link also seems to point to a dead link, but it has been kept because it might be a page which is only accessible through an internal network (since it's reserved for team members).
It does not appear to be used or maintained.
Centril
reviewed
Aug 5, 2019
| and can be browsed on the [perf website](https://perf.rust-lang.org). | ||
|
|
||
| [collector]: https://github.com/rust-lang-nursery/rustc-perf/tree/master/collector | ||
| [web frontend]: https://github.com/rust-lang-nursery/rustc-perf/tree/master/site |
Contributor
There was a problem hiding this comment.
Could we add a quick blurb about the most common use case and commands to achieve that?
@bors try
<wait a bit; copy the $hash from the build>
@rust-timer build $hash
Contributor
Author
There was a problem hiding this comment.
I've never used the rust-timer bot, but I added a small blurb. Ideally I would think documentation should be on the perf website (I searched around and couldn't find any anywhere, like who has permissions to use it, etc.).
Centril
reviewed
Aug 5, 2019
Centril
reviewed
Aug 5, 2019
| The state of tools included with Rust are tracked on the [toolstate | ||
| page](https://rust-lang-nursery.github.io/rust-toolstate/). When each PR is | ||
| merged via CI, the status of each tool is recorded in a JSON file and stored | ||
| in the [toolstate repo](https://github.com/rust-lang-nursery/rust-toolstate). |
Contributor
There was a problem hiding this comment.
Say something about the toolstate week and when it happens? cc @pietroalbini
Contributor
Author
There was a problem hiding this comment.
Toolstate is being documented in #243. This can link to that if/when that gets merged.
3525c78 to
e7ddba4
Compare
Contributor
|
I'm happy with this for the time being; we can make improvements if need be later. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is #144 rebased, and then with a bunch of my own updates.