Recently, my organization has started making use of the file path feature of the gerrit trigger plugin to support building subsets of a large git repo when changes are made. The idea is that, since we have a mono-repo with multiple projects that have dependencies on each other, changing code in a low level project will build all projects that depend on it as needed.

We discovered what appears to be a bug recently. One engineer was using a feature branch to get work done and pushed a merge commit to gerrit. Despite the merge touching multiple files, there were no conflicts, so the merge itself was a clean merge. In this case, even though files were changed in the merge that should match some of the file path definitions, none of the configured jobs were being triggered.

From what I can tell, it looks like the gerrit trigger plugin might be using the auto merge file list when managing file path comparisons for merge commits. My expectation is that the plugin would take into account all files that have changes compared to the base branch.