search

buildstream-migration / bst-staging

GNU Lesser General Public License v2.1
0 stars 0 forks source link

Replacement of artifact cache server for 2.0 #1323

Open Cynical-Optimist opened 4 years ago

Cynical-Optimist commented 4 years ago

See original issue on GitLab In GitLab by [Gitlab user @tristanvb] on May 28, 2020, 11:24

Our preference is to not maintain an artifact server, and to recommend better, more scalable CAS services in the REAPI space for this purpose.

In the event that there is not yet a good replacement for the artifact cache server provided by a third party project in the REAPI space by the time we are ready to release, then then we will keep bst-artifact-server as a thin layer around buildbox-casd.

Cynical-Optimist commented 4 years ago

In GitLab by [Gitlab user @tristanvb] on May 28, 2020, 11:48

marked this issue as related to #894

Cynical-Optimist commented 4 years ago

In GitLab by [Gitlab user @jjardon] on Jun 24, 2020, 09:22

For reference, good replacements exist for some time, so that should not be a worry: - buildbarn (It has being quite heavily tested already working with buildstream) - buildgrid? (I'm unsure of the amount of compatibility testing done)

Above is actually not going to be true soon, as buildstream moves to the asset-based -(API)-

Cynical-Optimist commented 4 years ago

In GitLab by [Gitlab user @abderrahimk] on Jun 25, 2020, 07:52

For now there is no replacement for the Artifacts and Sources services, and one needs to use bst-artifact-server --index-only in addition to whatever CAS server. This would change once we have #1272 and #1273, and we can recommend a solution that implements remote-asset too.

Cynical-Optimist commented 4 years ago

In GitLab by [Gitlab user @juergbi] on Jul 22, 2020, 15:08

marked this issue as related to #1371