[01:04:14] <wikibugs>	 10GitLab, 10Striker, 10Tools: Replace Diffusion integration with Gitlab integration in Striker (toolsadmin) - https://phabricator.wikimedia.org/T296893 (10mmodell) I'd like to automate management of git repos as well, for the sake of easy management and tracking what exists in gitlab, diffusion, gerrit and g...
[13:00:02] <jelto>	 Due to some updates gitlab.wikimedia.org won't be available for two to three minutes. I'll start with the update in around 15 minutes
[13:24:48] <jelto>	 GitLab should be up and running again
[15:15:44] <fab>	 Hi! Is it possible to create gitlab pages on the wmf gitlab infra? 
[17:14:22] <brennen>	 fab: not a feature we're supporting at this time.
[17:15:43] <legoktm[m]>	 I'm assuming/hoping that we'll keep supporting https://doc.wikimedia.org/ though, which is also a static site generator/publisher via CI, like gitlab pages, but more curated and controlled
[17:16:49] <brennen>	 yeah, our thinking was that we already have wikis and doc.wikimedia.org, and we didn't want to create more incentives to fragment docs further than they already are.
[17:21:32] <brennen>	 (i imagine we could revisit this at some point if people feel there's a strong need for it.)
[17:58:01] <nemo-yiannis>	 Hi, we are maintaining a tiny python cli codebase on gitlab (mostly for dogfooding/curiosity about gitlab CI) that we use in maps: https://gitlab.wikimedia.org/jgiannelos/maps-deduped-tilelist 
[17:59:12] <nemo-yiannis>	 When I started building it, runners where available to all users but i think lately this was restricted only to specific groups. Can we somehow re-enable CI ?
[18:03:44] <brennen>	 nemo-yiannis: runners are now available in /repos, which is our namespace for officially-supported projects
[18:04:06] <brennen>	 file a request for a group here and we can get you set up: https://phabricator.wikimedia.org/maniphest/task/edit/form/105/
[18:47:21] <fab>	 brennen thanks for the answer and the background.
[18:48:09] <brennen>	 sure thing
[18:51:39] <nemo-yiannis>	 Sounds good! Thanks
[18:52:13] <legoktm[m]>	 I do think it should be revisited in the future (like 1 year+) once we're more familiar with GitLab. https://salsa.debian.org/salsa-ci-team/pipeline/ has a neat feature where it builds the package and then publishes a full apt repository that people can use to install it for debugging, etc. I have dreams that something like that would lower the barrier to Debian packaging in Wikimedia
[18:55:47] <nemo-yiannis>	 Interesting, the reason I initially used gitlab CI was for building debian packages on each git tag: https://gitlab.wikimedia.org/jgiannelos/maps-deduped-tilelist/-/releases#0.0.4
[18:56:45] <nemo-yiannis>	 so for example here: https://gitlab.wikimedia.org/jgiannelos/maps-deduped-tilelist/-/pipelines/1312 it does all the check and then builds debian and python packages and then publishes them as artifacts
[19:12:38] <legoktm[m]>	 ooh, nice
[21:57:16] <wikibugs>	 10GitLab (Infrastructure), 10serviceops, 10Release-Engineering-Team (Radar): Self-reported GitLab SSH host key fingerprints don’t appear to match actual host key fingerprints - https://phabricator.wikimedia.org/T296944 (10brennen) p:05Triage→03Low We're using two separate sshd instances on gitlab1001 - o...