Skip to content

Update infrastructure page #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Aug 6, 2019
Merged

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented Aug 5, 2019

This is #144 rebased, and then with a bunch of my own updates.

chrisduerr and others added 7 commits August 5, 2019 13:32
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.
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Say something about the toolstate week and when it happens? cc @pietroalbini

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Toolstate is being documented in #243. This can link to that if/when that gets merged.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright; sounds good.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a link from here to the new page in #243.

@ehuss ehuss force-pushed the update-infrastructure branch from 3525c78 to e7ddba4 Compare August 6, 2019 02:24
@Centril
Copy link
Contributor

Centril commented Aug 6, 2019

I'm happy with this for the time being; we can make improvements if need be later.

@Centril Centril merged commit d203584 into rust-lang:master Aug 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants