Skip to content

Document rust-lang/rust CI artifact naming conventions #48

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.

Sign up for GitHub

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

Draft
jieyouxu wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Document rust-lang/rust CI artifact naming conventions #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,3 +64,19 @@ need to do so, please ask the infra team on Zulip.
>
> Storage space in ci-mirrors is not a concern. If you need to upload a new
> version of a file, add it separately without deleting the old one.

## Naming conventions

### Artifacts used by `rust-lang/rust` CI

For artifacts used by `rust-lang/rust` CI, they should adopt the following
naming convention:

* If the artifact is used by `crosstools-ng` ("CT-NG"), then CT-NG's mirror
artifact search logic requires the artifact to be directly available under
`rustc/`.
* Example: `rustc/linux-3.2.101.tar.gz` (the archive is used by CT-NG).
* If the artifact is used "ordinarily" and not by CT-NG, then the artifact
should be made available at preferably a "namespaced" path such as
`rustc/busybox/`.
* Example: `rustc/busybox/busybox-1.2.3.tar.bz2`.