The configuration cache report helpfully lists a set of inputs and appears to says which plugin contributed the input. Most entries are obvious but there are some, from a custom plugin, that I cannot find. Is there a way to find a more precise root location that added this input?
I suspect this information is not accurate as it seems to change from run to run, e.g. one particular file across three runs has been from a custom plugin then a gradle plugin (TestSuiteBasePlugin) then some 3rd party plugin (shadow) so it is presumably tracking when some particular lazy operation is triggered as opposed to the actual thing that adds the dependency?