[04:37:30] <wikibugs>	 10GitLab (CI & Job Runners), 10Patch-For-Review: Allow variants of rustlang/rust:nightly images on GitLab CI - https://phabricator.wikimedia.org/T326515 (10Legoktm)
[04:37:34] <wikibugs>	 10GitLab (CI & Job Runners), 10mwbot-rs: Unable to run Rust coverage reports in GitLab CI - https://phabricator.wikimedia.org/T325947 (10Legoktm)
[13:17:08] <wikibugs>	 10GitLab (Infrastructure), 10serviceops-collab, 10Patch-For-Review: Align and refactor GitLab restore scripts - https://phabricator.wikimedia.org/T326315 (10Jelto) Restore on GitLab replica `gitlab2002` failed because the rsync transfer of the backup took more time and was overlapping the beginning of the re...
[17:45:48] <kindrobot>	 Has there been any work, or is there any documentation about integrating Gerrit with GitLab CI? I.e. have a GitLab CI result be a voting step in verification?
[17:46:44] <kindrobot>	 I have a use case where this could help bridge our existing projects/workflow into GitLab without having to do it all-at-once.
[17:48:23] <kindrobot>	 I have a GitLab CI pipeline that deploys and runs e2e tests against a kubebernetes cluster. Most of our projects are still in Gerrit, so it would be great if those could trigger the GitLab CI run and vote based on the output.
[20:16:59] <kindrobot>	 I'm imagining something with webhooks on the GitLab CI side. Maybe we already to something similar with 
[20:17:39] <kindrobot>	 ...SonarQube bot
[20:42:52] <brennen>	 to my knowledge, this hasn't been worked on.  i think we had some discussion at one point but my feeling was kind of that it would be work to entrench something we're trying to get rid of.
[20:44:02] <brennen>	 to be fair, it might also be relatively trivial to just kick off a CI run.
[22:22:05] <kindrobot>	 OK, thanks for the context, I'll keep exploring it.