-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
ci: Upload/download from a new S3 bucket #44617
Conversation
r? @aidanhs |
This should land as a PR to bisect-rust first, adding these URLs to the list we look at, likely duplicating all of items. That way we don't break perf.rlo (yes, we should migrate this over to rust-lang-nursery probably). |
Note that this won't break anything, replication is set up so the objects should appear in rust-lang-ci as well |
As step 1, don't we need to do a copy from the east bucket to west, so that we have all the mirrored artifacts already there? E.g. I note I can't download https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror/2017-03-17-stamp-x86_64-unknown-linux-musl so I assume the same will be true for travis. |
I'm afraid this'll take long enough that we'd lose a build or two. I've mirrored the smaller folders like |
@bors r+ rollup If bors is happy then I am happy. |
📌 Commit a7144b6 has been approved by |
@bors r-
|
Moving buckets from us-east-1 to us-west-1 because us-west-1 is where rust-central-station itself runs and in general is where we have all our other buckets.
a7144b6
to
5cfee9b
Compare
@bors: r=aidanhs |
📌 Commit 5cfee9b has been approved by |
…1, r=aidanhs ci: Upload/download from a new S3 bucket Moving buckets from us-east-1 to us-west-1 because us-west-1 is where rust-central-station itself runs and in general is where we have all our other buckets.
…1, r=aidanhs ci: Upload/download from a new S3 bucket Moving buckets from us-east-1 to us-west-1 because us-west-1 is where rust-central-station itself runs and in general is where we have all our other buckets.
…1, r=aidanhs ci: Upload/download from a new S3 bucket Moving buckets from us-east-1 to us-west-1 because us-west-1 is where rust-central-station itself runs and in general is where we have all our other buckets.
[beta] Backport accepted PRs to 1.21 Backport of: - ~don't suggest placing `use` statements into expanded code #44215 - stabilize tcpstream_connect_timeout #44563 - stabilized iterator_for_each #44567 - travis: Move sccache to the us-west-1 region #44574 - stabilized ord_max_min #44593 - stabilized compiler_fences #44595 - ci: Upload/download from a new S3 bucket #44617 - stabilized needs_drop #44639 - Stabilized vec_splice and modified splice tracking issue #44640 - Backport libs stabilizations to 1.21 beta #44824
Moving buckets from us-east-1 to us-west-1 because us-west-1 is where
rust-central-station itself runs and in general is where we have all our other
buckets.