Get desktop application:
View/edit binary Protocol Buffers messages
This version number must always be present and can be used to further indicate presence or absence of parts of the proto at a later date. It only needs incrementing if a change to what is *mandatory* changes.
Core metadata
optional
digest of a Directory
The public data is a yaml file which is stored into the CAS Digest is of a directory
Zero or more log files here
digest of a directory
optional
digest of a directory
optional
The low/high diversity meta fields are digests of YAML files in which we store detatched metadata related to the artifact. metadata found in the low diversity file is expected to be frequently reused in the context of a given BuildStream project, ergo there is a very high chance that the entire content of the file can be shared across many artifacts. metadata found in the high diversity file is expected to diverge from one artifact to another. This still consists of metadata which does not directly affect an artifact's cache key, and as such cannot be stored directly in the proto itself.
Strict key is a later addition to the core metadata
digest of a directory
optional
optional
Information about the build dependencies
Used in:
The logs are stored in the CAS
Used in:
digest of a file
Used in:
This version number must always be present and can be used to further indicate presence or absence of parts of the proto at a later date. It only needs incrementing if a change to what is *mandatory* changes.
root directory digest of the files