[BuildStream] Coping with partial artifacts
- From: Sander Striker <s striker striker nl>
- To: BuildStream <buildstream-list gnome org>
- Subject: [BuildStream] Coping with partial artifacts
- Date: Thu, 1 Nov 2018 22:25:20 +0000
Hi,
I expect CAS and ArtifactCache (and ActionCache) to contain partial artifacts at some point due to different retention policies for different parts. For example, build trees might expire much faster than the core artifact (the part that is staged when depended upon). Similarly logs may expire as well.
This is all policy based, and very much use case specific. I do not wish for us to design or implement how partial expiry of artifacts might work, I merely want us to acknowledge that artifacts may become partial in the future. And with that acknowledgement consider future proofing buildstream to gracefully deal with partial artifacts.
Thoughts?
Cheers,
Sander
--
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]