This is a tracking bug. After consultation with rust team we will no doubt need to: * decommission existing buildbot jobs * monitor rust source code changes for triggering tasks (perhaps via bug 1158272) * set up a rust-specific windows worker type (and create ami) * set up mac builds with generic worker * set up linux builds with docker worker I'll await creating bugs to hang from this one until after we've consulted the rust team.

I've been experimenting with this in https://github.com/rillian/rust-build, and used it to build the linux toolchains in bug 1240982 on taskcluster, on top of my own build of the docker containers from https://github.com/rust-lang/rust-buildbot See the `tc` branch for attempts to automate task submission and upload. See also Ted's script at https://github.com/luser/breakpad-taskcluster/

Update based on private discussion: taskcluster isn't mature enough to hand the official rust builds at the moment. However, we'd still like to be able to run the rust packaging and/or custom toolchain builds used by the gecko build automation in taskcluster. Right now the repack and linux builds can run in task cluster, generating tooltool packages, but triggering those and patching the manifests to use the new builds is a manual process. The next step would be to trigger these as artifact-generating dependencies for the gecko taskcluster builds.

I am not sure where this has left off or where the Rust team would like to take it. We're always here to help if the Rust team would like to migrate more over to taskcluster. We now have all platforms migrated to taskcluster (with exception of some remaining hardware based tests that are awaiting new hardware).

I think bug 1455368 is the concrete next step for this bug, with later steps to be decided at that time. There doesnt' seem to be much use tracking here, as all dependent bugs are done. Pete, can we close plz?

Sure, thanks Dustin.