Recent addition of windows-shared-runners-manager switched me over to shared runners over my self-hosted one
Summary
I've been self-hosting a Windows machine for my GitLab CI runner across several repos. Within the last week, instead of choosing my self-hosted runner as it always has, it chose one of the windows-shared-runners-manager
runners instead, which broke my CI because it couldn't find an expected program:
https://gitlab.com/ssrobins/sdl2-example/-/jobs/410663632
I think the cause is that both the shared and the self-hosted runner use the windows
tag to select a runner. I would expect self-hosted runners to be chosen first before trying to select any shared ones. My workaround is to change my Windows tag in all my .gitlab-ci.yml files. Then it worked fine:
https://gitlab.com/ssrobins/sdl2-example/-/jobs/410686469
In general, changes to how runners are selected should not break existing workflows!
Output of checks
This bug happens on GitLab.com