Bitbucket Plugin Jenkins - Job Triggers Even Though No Changes In Included Regions

[adriaf]

I posted this on Jenkins too because I am not sure if the issue is in Jenkins or the Jenkins Bitbucket plugin or expected behaviour.  Jenkins jobs are triggering unexpectedly.

I have configured Bitbucket plugin for Jenkins and Webhook in Bitbucket Server.

Jenkins 2.319.1
BitBucket Plugin 1.1.11
atlassian-bitbucket-server-integration:2.1.3
BitBucket Server v7.17.1

I have Jenkins jobs configured for 

Build when a change is pushed to BitBucket

I have specified

Included Regions

and watching master branch

Day 1
Commit 1.  Merge Commit 1 into master with changed files in Included Regions.  The Jenkins job triggers as expected.

Day 2. 
Commit 2.  Merge Commit 2 into master.  Commit 2 has made no changes to any files in the Included Regions.   The Jenkins jobs triggers as if changes had been made to files in Included Regions.

I checked the webhook and the Request is sending a fromHash for Commit 1 and a toHash for Commit 2.   This appears correct.

The Jenkins job that triggers does a

git rev-list

back to Commit 1.    Is Jenkins/Bitbucket plugin looking at Commit 1 and re-executing the Jenkins job on Day 2 even though we now only care about Commit 2 on Day 2?   I would not expect the triggering changes associated with Commit 1 to cause the Jenkins job to execute again.