Access to and instructions for restarting Gitlab CI runners
@mikeperry and @jnewsome have both been doing some exciting stuff with our Gitlab CI recently and have run into some of the issues that happens every now and then. I think right now they depend upon an admin to kick the Gitlab CI service/machine in case it misbehaves and I was wondering if that is something Mike and Jim could get access to?
I'm writing this now particularly because Mike want to let the runners do a pretty big batch of experiments over the upcoming holiday and it would be sad if he needs to poke anybody for help in case of failure when nobody is around because they are taking time off.
I think the request is:
- Give Mike and Jim access to restart the Gitlab CI service (maybe as a reboot of the machine?)
- Do we have instructions for some of the failure modes or is it usually a restart?
Let me know what you think :-)