| Age | Commit message (Collapse) | Author |
|---|
|
... with entry for new just add-to-cas --resolve-special option.
|
|
|
|
...that checks if symlinks are treated the same as in just-mr.
|
|
...to check that --resolve-special option correctly stores entries.
|
|
|
|
|
|
|
|
...to remove the unnecessary link between folder name and the logic
of resolve_symlinks_map.
|
|
|
|
|
|
resolved.
|
|
|
|
|
|
... in particular in the case of targets producing precisely one
artifact; this better emphasizes the idea that we talk to the tool
in terms of targets. While there, also add some clarifying comments.
|
|
... as these are important features of the build tool. In particular,
target-level caching as a service is probably a unique feature.
|
|
The WithRetry function returns true upon success; therefore a
failure occured if the negation of the value is true. We should
report an error only in case of failure.
|
|
... describing the recent additions.
|
|
|
|
...and use std::unique_ptr for construction instead of std::optional.
|
|
... from the local file.
|
|
... from the local file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...and pass it to BazelCasClient
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...with direct access to mutable fields and drop additional deep copies.
|
|
|
|
|
|
|
|
|
|
|
|
...and remove ContentBlob.
|
|
|
|
...since it works with ArtifactBlobs only.
|
|
|
|
|
|
|
|
|
|
|
