Developers create a distributed cache definition file, naming the http/smb/ADO server and an optional telemetry server, and defining cache roles and policies. For example, dev machines always read from cache while CI loops read and write. Cache entries expire after 30 days (enforced by cache-writers).
Developers reference the definition file through kit configuration (CLI users) or directly in Metro configuration (manual integration).
If a telemetry server is specified, all layers of Metro caching, including the default in-memory and temp-disk layers, should be wrapped to report their hit/miss rate.
Build a distributed cache implementation for Metro using http/smb (file-server) or ADO (artifact store).
Detailed notes are in https://github.com/microsoft/rnx-kit/discussions/983.
Developers create a distributed cache definition file, naming the http/smb/ADO server and an optional telemetry server, and defining cache roles and policies. For example, dev machines always read from cache while CI loops read and write. Cache entries expire after 30 days (enforced by cache-writers).
Developers reference the definition file through kit configuration (CLI users) or directly in Metro configuration (manual integration).
If a telemetry server is specified, all layers of Metro caching, including the default in-memory and temp-disk layers, should be wrapped to report their hit/miss rate.
Write a suite of unit tests.