[14:43:13] 10GitLab, 10Release-Engineering-Team, 10serviceops-collab, 10Patch-For-Review: Align the GitLab runner tags - https://phabricator.wikimedia.org/T325069 (10Jelto) [14:57:32] Hi all! I asked in releng, but here is probably better, what's the current status of the untrusted gitlab runners? can anyone used them? (ex. toolforge users) if so how do I get them started? thanks! [15:09:18] dcaro: RelEng announced them in the last Tech All Hands ("Try it!"). It seems there is no documentation around that. I just added https://wikitech.wikimedia.org/wiki/GitLab/Gitlab_Runner/Cloud_Runners#Usage_of_Cloud_Runners [15:09:54] so if your gitlab ci job sets the tag: cloud, the jobs should be running on untrusted/cloud runners [15:14:27] with the exception that your project has to be in /repos/releng group. I guess the final configuration will look a bit different and accept all(?) groups/projects. [15:18:07] jelto: thanks! I guess that toolforge users (under cloud/toolforge-repos) might have to wait then? [15:20:16] actually, directly under /toolforge-repos [15:20:40] dcaro: that's my understanding from looking at the GitLab configuration yes. Folks from RelEng may add some more input here :) [15:33:10] hashar: ^ do you know if there's anything blocking us from allowing /toolforge-repos to use untrusted runners? [16:19:28] dcaro: I have no idea :( [16:20:08] I am also wondering whether we can have gitlab runners setup directly on toolforge, then I don't quite know anything about runners [16:42:43] dcaro: we're planning on opening untrusted runners to a wider audience early this year. We didn't want to unleash the world on them and then immediately go on vacation :) I think we're pretty much ready, but as noted here, we need to flip some configuration switches before others can use them. I expect they'll be ready to go within the next two weeks. [16:54:16] Awesome! Really looking forward to it :) [16:55:13] I'll be on PTO for a few weeks, but I definitely volunteer myself for early trials [17:00:49] \o/ nice: we love a good test subject :D We'll be sure to yell loudly on the mailing list once instances are available. [17:04:34] I'm pretty sure that there are a number of folks who would start putting CI in /toolforge-repos to use shortly after it is turned on. [20:46:35] 10GitLab (Infrastructure), 10serviceops-collab, 10Release-Engineering-Team (Yak Shaving πŸƒπŸͺ’), 10Upstream: Self-reported GitLab SSH host key fingerprints don’t appear to match actual host key fingerprints - https://phabricator.wikimedia.org/T296944 (10Dzahn) >>! In T296944#8486844, @Jelto wrote: > So we shou... [20:49:33] 10GitLab (Infrastructure), 10serviceops-collab, 10Release-Engineering-Team (Yak Shaving πŸƒπŸͺ’), 10Upstream: Self-reported GitLab SSH host key fingerprints don’t appear to match actual host key fingerprints - https://phabricator.wikimedia.org/T296944 (10Dzahn) 05Openβ†’03Resolved a:03Dzahn