We have a scenario where in one git repository two projects exists, where one does an includebuild of the other,.
We recently noticed that test tasks of the included project were not retrieved from the build cache if they were run from the including project. Meanwhile all compile jobs did work correctly with the cache.
After investigation we found that the computed build cache key was different when running test directly in the included project, compared to when running via the include build.
Further investigation showed that it was the input value for reports.enabledReports.html.displayName and
reports.enabledReports.junitXml.displayName that had a different value.
Finally, it seems that this value is something like “html report for Task ‘:included-project:subproject:test’” in the includebuild scenario, while in the main scenario the value is : “html report for Task ‘:subproject:test’”
Unfortunately, I have not been able to identify a way to override this value, due to which the the buildcache remains not fully functional for us.
As far as I can tell, this property is not actually ending up in the generated reports, so in fact - at least in this case- it seems that this property should not have been considered an input property for the cache.
However, I cannot oversee all possible usecases.
(Ps. obviously, it is not just the build cache that is blocked, the tasks inputs are considered dirty, triggering a re-run anyway)