Niels Möller nisse@lysator.liu.se writes:
I've now tried adding the "Run untagged jobs" for the runner. So if I understand it correctly, the tags don't belong to the runner machinery itself, they are attached on the association between runner machines and gitlab projects?
I've also pushed a branch ci-delete-tags-amd64 where I delete the tags from .gitlab-ci.yml.
Now builds successfully at git.lysator.liu.se (and the weird 403 problem has disappeared).
I see that I now get jobs started at gitlab.com, but they fail because
BUILDENV_NATIVE_IMAGE: nettle/build-images:buildenv-native
image: $CI_REGISTRY/$BUILDENV_NATIVE_IMAGE
I've pushed another change to that branch, replacing $CI_REGISTRY with a reference to git.lysator.liu.se:5050/. I wonder if there are any potential problems with having gitlab.com (and any other mirrors) pull images from that server? One would hope gitlab runners cache images, but I don't know. The server should have plenty of bandwidth, connected to the university network.
And now ci it gitlab.com is working too for this branch, see https://gitlab.com/gnutls/nettle/-/pipelines/2268610930. If I look at a random job, it is picked up by the runner "#12270845 (JLgUopmM) 1-green.saas-linux-small-amd64.runners-manager.gitlab.com/default". So it seems no tagging is required.
All jobs at gitlab.com succeeded except remote/s390x, which failed because I still had CI-variables set with a revoked ssh key. I've now deleted those variables, and job should hopefully be skipped based on job rules on next attempt.
And I also checked that the github mirror appears up-to-date, https://github.com/gnutls/nettle.
Thanks for the advice!
Regards, /Niels