4 ms·
Except it's more complex than that. Ideally you want to have multiple runners, and for them to scale so that developers aren't endlessly waiting in job queues.
by Aicy 5y ago
Except it's more complex than that.
Ideally you want to have multiple runners, and for them to scale so that developers aren't endlessly waiting in job queues. On top of that you might want proper network segregation, and for it to be on a separate virtual network to your workloads to reduce your blast radius. You might have problems with connecting your server to third party SaaS outside your network, etc etc etc
- dx034 5y agoA runner is super simple to set up and you once write a script and just deploy it a few times. Virtual network is also very easy to set up with most providers (even with dedicated servers), there's pretty much zero config. So far we didn't have any issues connecting to outside SaaS, but we host most stuff ourselves anyway, so that's not a common use case.
- vorpalhex 5y agoI run Gitlab runners for my social group.. It took about 20 minutes to setup and I don't think there has ever been a maintenance period for it other than a nightly upgrade/restart that is automated. I use docker for network isolation.