Hi there, I'm exploring the possibility of integrating the incremental compilation and remote cache features for a more efficient build process. In my current setup, I'm working with a clean environment where only a few modules normally do not leverage any caching mechanism. However, I believe using the latest uploaded cache as a foundation for incremental compilation could enhance efficiency. While I understand that expanding the number of modules could optimize cache utilization, I'm curious if integrating these two features could present a significant improvement on its own. In pipelines normally this is done by caching the main branch context, but I want to take advantage of the remote build cache and use this approach also for local environments. Is there an existing solution for this approach, or are there any plans to implement such feature in the near future? Thank you for your assistance!

The build cache caches the outputs of a task with it's inputs as key. So you have two problems. The information for incremental compilation is not a task output, so is not restored. And even if it would be, you would only get it for unchanged inputs. As soon as your inputs are different, you would not find the cache entry and so cannot do incremental compilation as nothing is restored