In Gerrit, how can I prevent the installation of a patch set that is not fully updated?

Question

Two developers work on the development area on two completely different changes (say, on two different files). Both of them simultaneously present their work, causing two Jenkins assemblies. These builds are going well, but one review takes longer than another.

The first dev sends its patch set, and there are no intermediate commits for development, so Gerrit merges it directly.

The second developer later sends his set of patches. Although there is now an intermediate commit, the merge itself is trivial, and Gerrit performs the merge.

Now we have two assemblies, none of which contain the work of the other.

I would like to block the second view if there are any intermediate commits, even if the merge would be trivial, forcing the developer to reinstall and update their view instead (and start a new build in Jenkins in the process).

What did I set in Gerrit to block such trivial, but unwanted merges when the check is completed, a set of patches is sent, but the target branch has intermediate merges on it?

Answer 1

You can change the project settings in Gerrit. To fast forward, this will prevent the change from moving because it is not a fast merge. Then, forcing developer2 to do git pull --rebase and click again, now the change that developer 1 made will be part of the test.