3 ms·
We are already paying Travis. > Given that Mozilla has their own extensive CI infrastructure While Mozilla does sponsor a lot of Rust stuff, it's fundamentall
by steveklabnik 9y ago
We are already paying Travis.
> Given that Mozilla has their own extensive CI infrastructure
While Mozilla does sponsor a lot of Rust stuff, it's fundamentally a community project, and so many of us (including myself) would prefer to not to move closer to something that's Mozilla-specific.
- JoshTriplett 9y agoThanks for the explanations. > We are already paying Travis. Have you heard anything from them about improving the issues with macOS? You've certainly got a case study in it being a problem. > While Mozilla does sponsor a lot of Rust stuff, it's fundamentally a community project, and so many of us (including myself) would prefer to not to move closer to something that's Mozilla-specific. Fair enough; I only suggested it because I had the impression that Mozilla's bits were all based on Open Source systems, and it would just be a matter of sharing hosting infrastructure rather than duplicating it.
- steveklabnik 9y agoI'm not on the infra team so I'm not sure; I do know they pay attention to this stuff though. Yeah, it's not really so much "it's not open source" as it is "Mozilla is the only organization who's really using this stuff". I used to worry about this a lot, but I think we've mostly gotten away from it now that a lot of organizations are using Rust. That is, if Rust was a Mozilla-only technology, I think Rust would have failed its mission. As such, I'm wary of things that seemingly tie Rust back into Mozilla too specifically.
- Kubuxu 9y agoIf I may ask, how did you made Travis take your money? We wanted to pay them (as an OSS project) for faster and more reliable builds for a long time but they always refused.
- steveklabnik 9y agoI wasn't directly involved, so I'm not sure. You should email the infrastructure team: infra-team@rust-lang.org
- jgraham 9y agoFWIW Mac jobs are also often capacity-limited on Mozilla infrastructure. It's not unusual to have thousands of jobs waiting on hundreds of machines, which leads to multi-hour queues at peak times. Fundamentally the problem with CI testing on Mac is that Apple don't provide the components you want to build a large pool of machines at reasonable cost, so everyone ends up doing slightly mad things involving hundreds of mac minis (obviously the Windows situation also isn't great; this kind of infrastructure loves free software on commodity hardware).