Closed Triqueon closed 5 months ago
Hello,
I have this issue with v2.0.3 on fresh install of ubuntu 22.04.4 LTS
Workaround: go to wherever the relevant machine stores galaxy roles (Default ~/.ansible/roles), clear out the riemers.gitlab-runner folder and clone this repo to that spot. That's neither nice nor a long-term solution, but will work for now.
Sorry about that, i'll see what i can do. I don't know if @guenhter can also do this. If not i'll explain it. Since last time it went all poof and it took a long time to get something restored.
I don't think I can create new releases because I don't have permissions to create tags or releases
@guenhter , i don't see an option to add you for tags. But even so it would require you to also allow imports on galaxy (unless that goes automatic, which it normally should though) funny i changed jobs. I am actually now back at the place where i started with this role and they have moved away from gitlab. The irony is high.
:)
Will this new release be added to Ansible Galaxy? It is still showing the old 2.0.3 version as latest.
Apologies, I was still using the old riemers.gitlab-runner
repo. I can see it now :)
Would it be possible to get a new release?
As far as I can tell, the version that ansible-galaxy installs is from last October, and appears to be broken for debian due to a missing condition on the Unhold Gitlab Runner version task. This is already fixed in this repository, but not yet present in upstream.