Remote executor and cache

[tsmarques]

Hi,

sorry if this is documented or has been answered somewhere but I haven't found a clear answer. I'm experimenting with remote executor and remote cache (--remote_executor and --remote_cache) and was wondering: Is there a point or benefit in running with both flags active (using the same endpoint)? e.g.

bazel build --remote_executor=<...> --remote_cache=<...>

What I'm wondering specifically is if running only with --remote_executor also builds a remote cache that can be used by others the same way as --remote_cache

thank you!

[tjgq]

The --remote_cache flag is redundant when set to the same value as the --remote_execution flag. The latter is sufficient to populate the cache for use by other builds.

…

On Wed, Apr 17, 2024 at 11:54 Tiago Sá Marques ***@***.***> wrote: Hi, sorry if this is documented or has been answered somewhere but I haven't found a clear answer. I'm experimenting with remote executor and remote cache (--remote_executor and --remote_cache) and was wondering: Is there a point or benefit in running with both flags active (using the same endpoint)? e.g. bazel build --remote_executor=<...> --remote_cache=<...> What I'm wondering specifically is if running only with *--remote_executor* also builds a remote cache that can be used by others the same way as --remote_cache thank you! — Reply to this email directly, view it on GitHub <#22030>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBK5HOJKUXTLM6WSI7EKRTY5ZBGJAVCNFSM6AAAAABGK7B4DCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGUYTQNBTGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[tsmarques]

Thank you for the clarification!