Hi, Le jeu. 23 juil. 2020 à 13:06, Tristan Van Berkom <[email protected]> a écrit : > I see a potential use case in the medium term for bst-artifact-server > even after BuildStream 2 is released: it may be a hard(ish) requirement > for users in a transitional period, for instance; I'm pretty sure we > will see a period of at least 1 year where freedesktop-sdk will need to > support both BuildStream 1 and BuildStream 2 (master on bst2 and bst1 > still required until stable is no longer supported).
I propose to use Remote Asset for this transition. As I mentioned in my earlier reply, RA is almost a superset of ReferenceStorage and we can make bst 1.x use RA for cache. I have implemented that in the following MR https://gitlab.com/BuildStream/buildstream/-/merge_requests/2000 I'd appreciate comments on this approach. I'm not sure about how to configure it: the current implementation uses RA if available and falls back to ReferenceStorage, without having extra configuration to select either one. This makes it transparently work with both the old artifact server and buildbox-casd. If we go with this approach, I believe we can simply drop bst-artifact-server as soon as 1.6 is released and recommend buildbox-casd by default for bst2 (and other CAS/RA implementations as they become ready). AFAICT, the only missing feature (except ReferenceStorage) is TLS client certificate authentication, which I think can be done with a reverse proxy. It would be interesting to provide example configuration for a reverse proxy that works though. Cheers, Abderrahim
