3 ms·
I saw a lot of projects build Windows artifacts with GitHub Actions. It doesn't seem too hard.
by maxloh 5y ago
I saw a lot of projects build Windows artifacts with GitHub Actions.
It doesn't seem too hard.
- nickysielicki 5y agoOkay, here’s an SDK I use. It’s 16GB. https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk#enterprise-wdk-ewdk https://docs.microsoft.com/en-us/windows-hardware/drivers/do... Show me how to use this with GitHub actions, if it’s not too hard.
- kilburn 5y agoI would use a self-hosted runner for that [1]. You can setup the SDK in that machine and it will be available for any jobs that end up running there. Depending on your requirements/scale the runner(s) can be a VM in your main machine, a cheapo dedicated server (hetzner/ovh) or even autoscaled hotspot instances in your preferred cloud. It is less pure than using GH's runners and having an end-to-end setup/teardown for your whole toolchain, but it would work just fine. Definitely better than without any CI.
- nickysielicki 5y agoIn practice, this is what I’m doing with Jenkins. But my point is that all of these container-first CI solutions lack relevancy for my team.