This message was deleted.
# develocity
s
This message was deleted.
s
We set this up to only publish to the remote from a CI job. Remote->local happens for all jobs (other thn this CI job ofc). That is the recommended approach afaik
I assume that is what you mean by "authentication for R/W"
d
If anonymous read access to the build cache isn't an option for you, there are not yet* any really good options:
• Use a single shared account and manage the password as a shared secret • Create a separate cache-read account for each user who requires acccess (* consolidating the core GE user accounts and the cache access accounts is on the roadmap)
r
Thanks for feedback, that answers my Q.