The ability to prevent P4-Plugin from running the p4 changes -m20 //depot/path/...@<last run>,<this run> in each run.
P4-Plugin runs the p4 changes -m20 command when the current build syncs to a label/change that is different from the one the last build synced.
The p4 changes command can be very expensive especially when a large label/change is involved. The comparison done using the command is not necessary when each build is independent of the previous one. The customer hoped that using the "Force clean and sync" option in the P4-Plugin would make each run ignore previous state information so that the P4-Plugin won't run the p4 changes -m20 command, but that was not the case.
The customer would like to have the ability to prevent P4-Plugin from running the p4 changes -m20 //depot/path/...@<last run>,<this run>.