What seems to be happening here is that there is some missing input to the task(s) in question, which means the build cache is serving you incorrect artifacts.
I suggest the following next steps:
- The next time your build fails in this way, publish a build scan from it. If you don’t have build scans enabled for all builds, you can publish the scan from the most recent build with the
buildScanPublishPrevioustask. See here for more documentation on publishing build scans. Once published, save the link to that scan. - Now, re-run the build with
--no-build-cache --scan. This will disable the build cache and publish a scan. Save the link. - Reply to this message with both scans.