If enabled, then running builds will be considered as reference build as well. Otherwise, only completed builds are considered. Enabling this option might cause problems if the reference build has not yet all the required results available.

If enabled, then the last completed build of the reference job will be selected if no other reference build can be found in the baseline, that contains the required commits or has the required build result. This is useful if you want to always compute a delta, even if the exact reference build cannot be found.

Defines the maximum number of commits that will be inspected to find the intersection between the current branch and the target branch (main branch). The default value is 100 commits. If a branch has more than the specified number of commits (since the last merge with the main branch), then the reference finder will stop and return an empty result. This helps to skip computations of delta results that contain too many differences.

The reference job is the baseline used to determine the relative differences to the current build. Several plugins that report build statistics (test results, code coverage, metrics, static analysis warnings) typically show their reports in two different ways: either as absolute report (e.g., total number of tests or warnings, overall code coverage) or as relative delta report (e.g., additional tests, increased or decreased coverage, new or fixed warnings). To compute a relative delta report, a plugin needs to select another build to compare the current results to (a so-called reference build). This reference build is obtained from the specified reference job.

In Multibranch Pipelines this parameter can be left empty: in these jobs, the plugin selects the build automatically from the associated job that builds the main target branch. For all other jobs, the last completed build of the current job will be used as reference build if the reference job is not specified.

When a reference build is searched for in the baseline (see the parameter reference job) then it sometimes makes sense to only consider builds that have a certain result. For example, you may want to skip the computation of a delta coverage when the reference build has failed tests. Or you may want to skip the computation of new warnings when the reference build has a compilation error. The following enumeration shows the possible values for this parameter and the corresponding behavior:

SUCCESS

The selected build must be successful

UNSTABLE

The selected build must be successful or unstable

FAILURE

The result of the build is not relevant (this is the default behavior if unset)

If enabled, then a build of the reference job will be skipped if one of the commits is unknown in the current branch. This is useful if you want to compute the delta only with builds that contain all the commits that are part of the current job. That means that the reference will not contain newer and unrelated commits that may affect the build results.