ci: Upload/download from a new S3 bucket

[alexcrichton]

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.

[alexcrichton]

r? @aidanhs

[alexcrichton]

cc rust-lang/rust-central-station#22

[Mark-Simulacrum]

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

[alexcrichton]

Note that this won't break anything, replication is set up so the objects should appear in rust-lang-ci as well

[aidanhs]

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.

[alexcrichton]

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?

I'm afraid this'll take long enough that we'd lose a build or two. I've mirrored the smaller folders like rust-ci-mirror (but botched the permissions so you couldn't download, should be fixed now), but the big folders like rustc-builds can start getting transferred once this is landed.

[aidanhs]

@bors r+ rollup

If bors is happy then I am happy.

[bors]

📌 Commit a7144b6 has been approved by aidanhs

[aidanhs]

@bors r-

[00:03:32] tidy error: /checkout/src/ci/docker/scripts/sccache.sh:14: line longer than 100 chars

[alexcrichton]

@bors: r=aidanhs

[bors]

📌 Commit 5cfee9b has been approved by aidanhs