` Way to do CI for a project with a huge toolchain? » Motion design agency graphics studios

Way to do CI for a project with a huge toolchain?

Hi, I am maintaining a fork of . This builds to Windows, Android, Linux and Mac.

I'd like a CI solution mainly to handle building and deploying because we are a small team and I don't want to be building for all these platforms manually.

WebRtc however uses Google's . The toolchain and its dependencies are huge () - before we've even checkout out the fork - then actually setting them up automatically is not so straightforward (one has to explicitly accept the ndk eula for example, and update a file nominating the targets).

It seems something like Travis builds a fresh VM each time, which isn't going to work with depot_tools. On the other hand, I don't want to have a load of VMs sitting around doing nothing 99% of the time and still have to be invoked manually.

Is there a service for open source projects that would support something like this? (Something like, I build the base VM, then the CI solution uses that to check out and build the repo?)

submitted by
---
[fixed][/fixed]
jodo