Hello

First of all thanks for this great ecosystem of user-friendly warning & coverage parsing plugins

In short, I would like to disable reference build discovery in coverage reports generation. 

Use-case

I have a (multi-branch) jenkins job where each job can build different "variants" based on user parameters .

The "variant" selection will impact what is compiled, what is run, and therefore which warnings and which coverage result.

The same job will usually be alternatively triggered between variant_A and variant_B.

(More details: in reality I have ~30 variants. Job tests all pull request. Having a single job for all these variants has several benefits:  memory saving (branch will not cloned 30 times), it allow users to quickly re-test a single variant,  reporting is clearer than having a huge pipeline with many steps)

Problem

In such setup, the reference build makes little sense since it will usually find the previous build.For the warnings reporting, I found the 

recordIssues(skipBlame : true)

  option very convenient. However I can't find a way to do the same thing with the recordCoverage equivalent.

Solutions?

Having such disable option would help such use-cases.

Alternatively, the reference finder algo  (git-forensic-plugin IIUC) could perhaps take into account the build parameters to find the correct reference build, but I guess it's a lot of work.