3 ms·
> GitHub Actions, et. al. cannot touch the target environments that we deploy our software to. It can with on-prem self-hosted Runners > https://docs.github.co
by ElijahLynn 6y ago
> GitHub Actions, et. al. cannot touch the target environments that we deploy our software to.
It can with on-prem self-hosted Runners > https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners https://docs.github.com/en/actions/hosting-your-own-runners/...
I just had this same complaint about using Actions and was pointed to this document.
- cyberpunk 6y agoYeah and that's a total shitshow too. You want to run that in k8s? * First off it won't work with a musl image * You need to request a new token every 2 hours * It doesn't spawn pods per build like gitlab, it's literally a dumb runner, the jobs will execute *IN* the runner container, so no isolation, and you need all the tools under the sun installed in the container (our runner image clocked in at 2gb for a java/node stack) * Get prepared for a lot of .net errors on your linux boxes (yes, not exactly a showstopper but.. urgh). I hated my time with GitHub actions and will not miss it.
- Mic92 6y agoYeah. I really hope they fix the dumb runner part: https://github.com/actions/runner/pull/660 https://github.com/actions/runner/pull/660 I resorted to this one instead https://github.com/summerwind/actions-runner-controller https://github.com/summerwind/actions-runner-controller but it requires kubernetes...