Optimized build configuration.

[mvastarelli]

Is there anything that can be done to speed up the build process in GitHub? Perhaps switch to using linux clients or yarn over npm? We have 3000 build minutes/month and each individual build takes 5:30-6 minutes on average. Right now we're nowhere near the limit (176 minutes) so there isn't any concern, but ideally I'd like to prevent this from potentially becoming an issue.

[mvastarelli]

@evan-cohen I configured a self-hosted runner using one of my crypto-mining rigs so you should be able to use the runs-on: self-hosted option in the build configurations. The machine is an AMD 5900x with 8GB RAM with a 40GB NVME drive running HiveOS, which I think is based on Ubuntu 16x. The machine runs 24-7 so it should always be available.

Let me know if it helps. If this solution works I'll re-tool the server to run Ubuntu 20x and run 100% off the NVME drive (currently the OS is installed on a flash drive).

[mvastarelli]

Configured self-hosted build agent using spare CPU mining rigs. Reduced build times from ~6 minutes down to around ~2:40. In addition, since the build agents are now self-hosted there's no concern of overages with GitHub's compute limits.