[10:29:32] 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team, 13Patch-For-Review: Upgrade GitLab to major version 17 - https://phabricator.wikimedia.org/T365675#9854243 (10Jelto) [10:36:30] 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team: Upgrade GitLab to major version 17 - https://phabricator.wikimedia.org/T365675#9854271 (10Jelto) >>! In T365675#9842110, @jnuche wrote: > > Can't speak for other tools, but Kokkuri uses the new id tokens instead of the old depr... [12:45:59] Hi all, would it be possible to run a VM on a gitlab runner? This would be for toolforge, where we need a complex setup (k8s/harbor/...) to be able to run functional tests. I would be interested even if we would be the ones providing the runner [13:49:11] 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team: Upgrade GitLab to major version 17 - https://phabricator.wikimedia.org/T365675#9854865 (10brennen) > @brennen if you have a few minutes I'd be happy if you go over https://docs.gitlab.com/ee/update/deprecations.html?removal_mile... [13:53:21] 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team: Upgrade GitLab to major version 17 - https://phabricator.wikimedia.org/T365675#9854876 (10brennen) > The only thing I noticed was Offset pagination for /users REST API endpoint is deprecated. I wondered if this would hit gitlab-... [14:07:22] dcaro: currently we only support container workloads on the officially supported runners. However it would be possible to setup and register your own runner (for example as a VM in wmcs) and run any command you want (in docker or as a shell command) [14:09:11] jelto: nice, I'd be interested in that (also, running that way allows us to not abuse the shared runners for heavy tests), are there any guidelines I can follow? [14:46:20] i don't think we have a lot of docs specific to bringing your own runner in our environment, but i know some users are doing so... [14:46:55] https://www.mediawiki.org/wiki/GitLab/Workflows/CI is pretty sparse [14:47:40] The general instructions for installing a runner are here: https://docs.gitlab.com/runner/install/ [14:47:50] https://docs.gitlab.com/runner/executors/ gives some options [14:59:22] 10GitLab (Pipeline Services MigrationšŸ¤), 10Data-Engineering (Q4 2024 April 1st - June 30th), 10Event-Platform, 13Patch-For-Review: Migrate Data Engineering Pipelinelib repos to GitLab - https://phabricator.wikimedia.org/T344730#9855241 (10tchin) >>! In T344730#9848618, @Ottomata wrote: > Added jsonschema-t... [15:36:18] 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team: Upgrade GitLab to major version 17 - https://phabricator.wikimedia.org/T365675#9855435 (10bd808) >>! In T365675#9854875, @brennen wrote: >> The only thing I noticed was Offset pagination for /users REST API endpoint is deprecate... [15:39:54] 10GitLab (Pipeline Services MigrationšŸ¤), 10Data-Engineering (Q4 2024 April 1st - June 30th), 10Event-Platform, 13Patch-For-Review: Migrate Data Engineering Pipelinelib repos to GitLab - https://phabricator.wikimedia.org/T344730#9855455 (10Ottomata) > Should I merge and deploy this MR before it gets migrate... [16:11:13] 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team: Upgrade GitLab to major version 17 - https://phabricator.wikimedia.org/T365675#9855610 (10brennen) We could probably bump https://gitlab.devtools.wmcloud.org/ to v17... [20:30:51] 10GitLab (Pipeline Services MigrationšŸ¤), 10Data-Engineering (Q4 2024 April 1st - June 30th), 10Event-Platform, 13Patch-For-Review: Migrate Data Engineering Pipelinelib repos to GitLab - https://phabricator.wikimedia.org/T344730#9857030 (10Ottomata) [20:51:55] 10GitLab (Pipeline Services MigrationšŸ¤), 06Growth-Team, 10Image-Suggestion-API: Migrate image-suggestion-api to GitLab - https://phabricator.wikimedia.org/T344740#9857125 (10Urbanecm_WMF) 05Openā†’03Declined Filled {T366534} to archive the repository instead; it is no longer necessary.