zuul/zuul
Code Issues Proposed changes

Add a note about Zuul not handling Gerrit chagne number collisions

Browse Source 
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
This commit is contained in:
Clark Boylan
2024-11-04 12:56:25 -08:00
parent b346aa80b1
commit 34df33ebdc
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/drivers/gerrit.rst
View File

@@ -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
------------------------