hey marco, What your looking for (imo) is not a gerrit change. Its a jenkins side change
https://gerrit.fd.io/r/10237 Note: I also included not running on trivial rebase which may freak some people out. You cant just gerrit-trigger-patch-submitted because the way they roll everything up and up and up it would change behavior of all projects (outside of vpp) using that global trigger. I have no plans on advancing this patch..only pointing out one way to do it. Ed On Jan 24, 2018, at 4:13 AM, Marco Varlese <mvarl...@suse.de<mailto:mvarl...@suse.de>> wrote: All, I noticed that when a patch is updated solely for the commit message (and pushed to gerrit), gerrit triggers a complete new build. I wonder if it is possible (on the gerrit backend) to catch that a patch has been submitted with only the commit-message being updated hence skipping the full verification process? I am thinking about it since we could save cycles (many) on the build-machines between the many processes building the code on various distros. Thoughts? Cheers, -- Marco V SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
