Q:

Jenkins Gerrit-Trigger plugin: How to start build for each push instead of each commit

We are using Jenkins,GerritTrigger setup for CI and it will start build for each commit though all commits came from single push.  Since all changes are dependent on each other its enough to make a single build with all changes, but I don't see that option in GerritTrigger plugin. 
I believe many companies use Jenkins and Gerrit combination and I am curious to know how they are handling these cases. 
Example:
If a developer pushes below 4 commits at once to gerrit it will create 4 changes accordingly in gerrit say 1,2,3,4 and it starts 4 builds in jenkins for all commit
git log --oneline

e3dfdwd CommitD
5fgfdgh CommitC
df34dsf CommitB
a23sdr3 CommitA 

Here 4 commits as a whole will pass all tests in jenkins but individually they will fail.  Now jenkins builds will fail for A, B, C and will succeed for D as it will checkout A,B,C as they are its dependencies. 
In this case though Commit-D is successful it can't be merged as its dependencies are not passed in Jenkins. 
It seems reasonable from development to expect jenkins verification for each push instead of each commit.  But GerritTrigger can run for each commit only. 
Question:
Is there a way to inform jenkins to start build only for commit-D as it will have all dependencies C,B,A ?? 
Or can we start a build for each git push from development instead of commits? 
Sorry if I had any info

A:

I found a way to start build only for commit-D. 
I have introduced a gerrittrigger job which runs immediately after every commit, this job will not do any clone/build/verification.  
It will just do some set of verifications like, check if given change has needed-by change, dependency exists and dependencies on same branch etc
This job will trigger another main job which does real clone, checkout change, build, verification etc only for changes which pass all validations. 
So this will start job always for top commit and approve/reject all dependent changes based on job result. 
Though it has few limitations, we found this method is suitable for our workflow

