From 34df33ebdc32c20da00c411f9694e12138f4ef8c Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Mon, 4 Nov 2024 12:56:25 -0800 Subject: [PATCH] Add a note about Zuul not handling Gerrit chagne number collisions Since Gerrit 3.7 it has been possible to import projects and their changes from one Gerrit server to another. Doing so may result in change number collisions. The only unique way to identify changes in this situation is with a project,changenumber tuple. Zuul's Gerrit driver currently expects changes to be uniquely identified by a change number document this expectation. Change-Id: I26e785f1decbcf7065d8ad39f2c051e31360d8b8 --- doc/source/drivers/gerrit.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/source/drivers/gerrit.rst b/doc/source/drivers/gerrit.rst index ecdfd6247a..321bf7c0bd 100644 --- a/doc/source/drivers/gerrit.rst +++ b/doc/source/drivers/gerrit.rst @@ -50,6 +50,14 @@ settings for different connection methods follow. is changed while Zuul is running, all running Zuul schedulers should be restarted in order to see the change. +.. note:: + + Since Gerrit 3.7 it has been possible to import projects and their + changes from one Gerrit server to another. Doing so may result in + change number collisions (change numbers that do not uniquely identify + a single change). Zuul's Gerrit driver is not currently expected + to work with non unique change numbers. + Connection Configuration ------------------------