[JENKINS-32386] Polling Ignores Commits In Certain Paths feature fails to work when changes are merged from a branch onto the branch that is being polled

We use Polling Ignores Commits in Certain Paths option to poll for changes in a specific directory of the git repo. It works smooth until we merge changes from another branch onto the polled branch.

Even though the merged changes don't come under the Included Regions, builds get triggered.

Job Config looking for changes only under "harsha" directory.

Build triggered by changes polled under a different directory

Ideally even when the merge happens, the plugin should trigger changes based on the included regions.

We use Polling Ignores Commits in Certain Paths option to poll for changes in a specific directory of the git repo. It works smooth until we merge changes from another branch onto the polled branch. 

Even though the merged changes don't come under the Included Regions, builds get triggered. 

Job Config looking for changes only under "harsha" directory.


Build triggered by changes polled under a different directory


Ideally even when the merge happens, the plugin should trigger changes based on the included regions.

• environment: Jenkins - 1.580.3, Git Plugin - 2.4.1 (was seen in 2.4.0) too,

Start in the git-plugin polling implementation and reproduce the case where a merge into the polled branch changes paths outside the configured "harsha" included region. Trace how polling evaluates merge changes, then add coverage for this scenario; done means builds trigger only when included regions changed.