Continuously publish Cargo builds #3239
Conversation
|
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
|
Oh I should also mention that I took the liberty of deleting all the weird snapshot and rustc downloading business. The configure script now just assumes you've got |
|
Beautiful! |
|
@bors r+ Seems good, though I'm not sure about putting this in its own bucket instead of on static.rlo. The new bucket doesn't matter much to me in the short-term though. |
|
📌 Commit fb85de8 has been approved by |
|
⌛ Testing commit fb85de8 with merge 87b72bc... |
|
💔 Test failed - cargo-linux-64 |
|
@bors: r=brson |
|
📌 Commit bbe5df7 has been approved by |
|
⌛ Testing commit bbe5df7 with merge 1bde79b... |
|
💔 Test failed - cargo-win-msvc-64 |
|
@bors: r=brson On Fri, Nov 4, 2016 at 3:34 PM, bors notifications@github.com wrote:
|
|
📌 Commit 9c30d75 has been approved by |
|
⌛ Testing commit 9c30d75 with merge b259030... |
|
💔 Test failed - cargo-mac-64 |
This commit tweaks Cargo's automation to continuously publish builds on Travis an AppVeyor. Once this is merged we can hopefully turn off all buildbot automation related to Cargo and purely rely on Travis and AppVeyor for this repository. All CI matrices are ported over to Travis and AppVeyor and a new musl build of Cargo is even added just to test out adding that for a spin. Currently Cargo will upload the final artifact for each target to a directory keyed by the commit hash to a new bucket on S3, rust-lang-cargo-dev. Once we're happy with the builds then we can change this to `rust-lang-cargo` or anything else at that point.
|
@bors: r=brson |
|
📌 Commit 7799014 has been approved by |
|
⌛ Testing commit 7799014 with merge 96147aa... |
|
💔 Test failed - cargo-mac-64 |
|
@bors: retry On Sun, Nov 6, 2016 at 10:44 PM, bors notifications@github.com wrote:
|
Continuously publish Cargo builds This commit tweaks Cargo's automation to continuously publish builds on Travis an AppVeyor. Once this is merged we can hopefully turn off all buildbot automation related to Cargo and purely rely on Travis and AppVeyor for this repository. All CI matrices are ported over to Travis and AppVeyor and a new musl build of Cargo is even added just to test out adding that for a spin. Currently Cargo will upload the final artifact for each target to a directory keyed by the commit hash to a new bucket on S3, rust-lang-cargo-dev. Once we're happy with the builds then we can change this to `rust-lang-cargo` or anything else at that point.
|
☀️ Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
How can I access it? |
|
@jirutka they're all available at |
This commit tweaks Cargo's automation to continuously publish builds on Travis
an AppVeyor. Once this is merged we can hopefully turn off all buildbot
automation related to Cargo and purely rely on Travis and AppVeyor for this
repository. All CI matrices are ported over to Travis and AppVeyor and a new
musl build of Cargo is even added just to test out adding that for a spin.
Currently Cargo will upload the final artifact for each target to a directory
keyed by the commit hash to a new bucket on S3, rust-lang-cargo-dev. Once we're
happy with the builds then we can change this to
rust-lang-cargoor anythingelse at that point.