Description of the feature request:
I would like to be able to use the --disk_cache as a read/write cache, but the remote cache as a read-only cache. I thought --noremote_upload_local_results would do this, but it seems that flag is just overridden by the --disk_cache option. It seems this is the expected behavior, since in #7512, I see it says:
On put, Bazel will store items in both the disk and the HTTP cache.
Could this be changed to support this mixed use case?
What underlying problem are you trying to solve with this feature?
We are still in the process of moving our build to bazel, and not all builds on dev machines are safe to be pushed to the shared remote cache, so we only populate the remote cache from CI builds. Being able to have a local cache is very helpful when switching between dev branches for super fast builds. Our current workaround is to run a remote cache on every machine that acts as a proxy to the real shared cache, but we would like to move away from all of that overhead.
Description of the feature request:
I would like to be able to use the
--disk_cacheas a read/write cache, but the remote cache as a read-only cache. I thought--noremote_upload_local_resultswould do this, but it seems that flag is just overridden by the--disk_cacheoption. It seems this is the expected behavior, since in #7512, I see it says:Could this be changed to support this mixed use case?
What underlying problem are you trying to solve with this feature?
We are still in the process of moving our build to bazel, and not all builds on dev machines are safe to be pushed to the shared remote cache, so we only populate the remote cache from CI builds. Being able to have a local cache is very helpful when switching between dev branches for super fast builds. Our current workaround is to run a remote cache on every machine that acts as a proxy to the real shared cache, but we would like to move away from all of that overhead.