On Tue, 2020-07-07 at 10:24 +0200, Sander Striker via buildstream-list wrote: > On Tue, Jul 7, 2020 at 10:11 AM William Salmon <[email protected]> > wrote: > > > > Not supporting the bst1.x api would be very inconvenient for early > > adopters who already use bst1.x > > > > Many members of the bst community that i know have there own bst cache > > server that they define in there ~/.config/buildstream.conf > > > > Having to have to run two servers and two ~/.config/buildstream.conf and > > all the added cli to use them would be a real faf, and add quite a lot > > of real friction. > > Can we walk through the steps of what that will actually look like?
master already supports buildstream2.conf in addition to the unversioned buildstream.conf to make it easier to use both bst1 and bst2. I thus don't consider the config aspect a blocker. > > > I would be strongly in favor of keeping this as at least optional > > behavior in the server until a good bit after bst2 is released as it is > > unlikely that all downstream projects will just switch imitatively. > > -1. I'd like the 2.0 release to actually be a point where we can > shed old APIs and interfaces. Keeping ReferenceServer in signs up > for supporting it throughout 2.x. I agree. The goal for 2.0 is to completely drop bst-artifact-server and thus also drop the ReferenceStorage server support from the BuildStream code base. However, if there is no suitable replacement in time for 2.0, it may make sense to move bst-artifact-server to a separate repository to make it clear we don't want to maintain bst-artifact-server long term as part of BuildStream core. In that separate repository I wouldn't mind keeping the ReferenceStorage server part for bst 1.x compatibility if there is interest. And if there is an interested maintainer we could have bst-artifact- server in a separate repository even if there is a suitable replacement in time for 2.0. This could be done at any time after the merge of !1978. Prerequisite is #1371. Based on the above my plan would be to keep ReferenceStorage server support in master for now, however, it will be dropped from the BuildStream core repository before 2.0. Either dropped completely or moved to a separate repository. Does this sound like a reasonable way forward to everyone? Cheers, Jürg
