Instructions for setting up a Salsa runner

[Soren Stoutner]

Does anyone have any experience/know of any current instructions for setting
up a Salsa runner. These two appear to be incomplete or outdated:

https://wiki.debian.org/Salsa/Doc/CustomRunners/SystemdNspawnRunner

https://salsa.debian.org/federico/gitlab-runner-nspawn/

My motivation for doing so is that I am working on pyinstaller, which requires
more than 3 hours to build (which is the runner timeout).

https://salsa.debian.org/soren/python-pyinstaller/-/jobs/6628551

I would like to take advantage of Salsa CI, and am fine setting up a runner on
my hardware, but I don’t really know what I am doing and am struggling to get
it all the way configured. This is as far as I got:

https://salsa.debian.org/soren/python-pyinstaller/-/jobs/6629094

[Soren Stoutner]

Post by Soren Stoutner
Does anyone have any experience/know of any current instructions for setting
https://wiki.debian.org/Salsa/Doc/CustomRunners/SystemdNspawnRunner
https://salsa.debian.org/federico/gitlab-runner-nspawn/
My motivation for doing so is that I am working on pyinstaller, which requires
more than 3 hours to build (which is the runner timeout).
https://salsa.debian.org/soren/python-pyinstaller/-/jobs/6628551
I would like to take advantage of Salsa CI, and am fine setting up a runner on
my hardware, but I don’t really know what I am doing and am struggling to get
https://salsa.debian.org/soren/python-pyinstaller/-/jobs/6629094

I was able to figure out how to set one up using the Docker executor. I
updated the documentation on the wiki with the information for the next person
who needs to do this.

https://wiki.debian.org/Salsa/Doc/CustomRunners

P.S. Running things in a Docker container is insanely slow compared to bare
metal. A build that takes an hour on bare metal takes more than four hours in
GitLab Runner with a Docker executor. (Which is why I needed to setup my own
runner, so I could set the reprotest timeout to at least 10 hours.) I can’t
even imagine what Salsa CI on the qtwebengine-opensource-src or chromium
packages would look like. Maybe I will enable Salsa CI on qtwebengine-
opensource-src and find out.