We have a CI job that triggers following a PR submit/update. The job has a `PR_NUMBER` parameter which is used later during the build,

In the case of a few PR updates, one after another, each will trigger a build which causes a few builds running against the same PR but  only the last one is relevant,

When using the `Throttle Concurrent Builds` plugin with the `Prevent multiple jobs with identical parameters...` option, the functionality of pausing new builds with the same parameters works perfect, but we need it reversely,

The suggestion is to add an `inverse` option that will abort previous builds triggered with the same parameters, and maybe also throw an exception/msg to the aborted build "This build aborted by <build.number> due to..."