[08:46:11] 10GitLab (Infrastructure), 10Release-Engineering-Team, 10serviceops, 10serviceops-collab, 10User-brennen: GitLab major release: 15.x - https://phabricator.wikimedia.org/T309062 (10Jelto) > Based on last time, we should give this a month or so to bake in; filing now for planning purposes. As best I unders... [16:42:38] 10GitLab (Infrastructure), 10Release-Engineering-Team, 10serviceops, 10serviceops-collab, 10User-brennen: GitLab major release: 15.x - https://phabricator.wikimedia.org/T309062 (10brennen) > The release of GitLab 15 was two month ago. GitLab 15.2 was released last week too. Do you have any plans/preferen... [16:43:54] 10GitLab (Infrastructure), 10Release-Engineering-Team, 10serviceops, 10serviceops-collab, 10User-brennen: GitLab major release: 15.x - https://phabricator.wikimedia.org/T309062 (10brennen) Based on past experience, it does seem likely that we can expect a critical security release that hasn't been backpo... [17:05:10] 10GitLab (CI & Job Runners), 10Security-Team, 10serviceops, 10Patch-For-Review, and 2 others: Setup GitLab Runner in trusted environment - https://phabricator.wikimedia.org/T295481 (10sbassett) @Jelto - From a security perspective, as long as `$GITLAB_TOKEN`'s value is never disclosed in any public, CI-rel... [17:18:17] 10GitLab (Project Migration), 10Release-Engineering-Team: Create new GitLab project group: wm-juniors-il - https://phabricator.wikimedia.org/T313750 (10GBecher1) [21:25:06] hey folks, i'm going to be testing https://gerrit.wikimedia.org/r/c/operations/puppet/+/815769 for a bit. i'll disable puppet on all the non-trusted runners in the gitlab-runners project before doing so to mitigate risk of disruption but there's a possibility for it on at least one of the runners [22:16:40] alrightly. all done. seems to work! [22:17:18] the approach is still a little funny but at least it's properly parsing toml now and not doing so much bash hackery [23:07:34] yeah, seems overall like a more robust way to do it.