Age | Commit message (Collapse) | Author | |
---|---|---|---|
2025-01-07 | Add backend description to CAS in a ctor of TargetCache | Maksim Denisov | |
...instead of adding it preliminarily. | |||
2025-01-07 | TargetCache: use BackendDescription for sharding instead of a plain string | Maksim Denisov | |
2025-01-07 | Store BackendDescription in StorageConfig | Maksim Denisov | |
...instead of a plain hash. Hash gets computed for different storage types on the fly. | |||
2025-01-07 | TargetCache: employ the shard even for a default constructed object | Maksim Denisov | |
...since this is a more generic approach. | |||
2025-01-07 | Pass BackendDescription to StorageConfig from the outside | Maksim Denisov | |
2025-01-07 | Pack BackendDescription to a class | Maksim Denisov | |
...to let it be stored as an independent instance. | |||
2024-12-20 | clean up dependencies | Klaus Aehlig | |
2024-12-20 | TreeStructure: make just-mr aware of "tree structure" roots | Maksim Denisov | |
2024-12-20 | TreeStructure: support parsing in just-mr | Maksim Denisov | |
2024-12-20 | TreeStructure: Unify parsing of precomputed roots in just-mr | Maksim Denisov | |
2024-12-19 | TreeStructure: evaluate roots. | Maksim Denisov | |
2024-12-19 | TreeStructure: Implement computation logic | Maksim Denisov | |
2024-12-19 | TreeStructure: Implement cache with uplinking | Maksim Denisov | |
2024-12-19 | Implement TreeStructureRoot | Maksim Denisov | |
2024-12-19 | FileRoot: disclose RootGit data. | Maksim Denisov | |
2024-12-19 | Move functionality for staging from CAS to output paths to TreeReader | Maksim Denisov | |
...and employ it in LocalApi. | |||
2024-12-19 | Remove FileRoot::ComputedRoot | Maksim Denisov | |
2024-12-19 | Use PrecomputedRoots during evaluation | Maksim Denisov | |
2024-12-19 | Support substitution of precomputed roots in RepositoryConfig | Maksim Denisov | |
2024-12-19 | Support PrecomputedRoots in FileRoot | Maksim Denisov | |
2024-12-19 | Implement PrecomputedRoots | Maksim Denisov | |
...that is an abstract representation of roots that must be computed before the start of the main build. | |||
2024-12-19 | Fix cause of minor warnings | Oliver Reiche | |
2024-12-19 | Fix struct member initialization | Oliver Reiche | |
2024-12-19 | Remove unused headers | Oliver Reiche | |
2024-12-19 | Remove unused function | Oliver Reiche | |
2024-12-19 | Remove unneeded compat_storage | Oliver Reiche | |
2024-12-19 | Remove unnecessary moves | Oliver Reiche | |
2024-12-19 | JustMr: update output config for computed roots | Maksim Denisov | |
2024-12-12 | Computed roots: normalize build arguments | Klaus Aehlig | |
While building a computed root generally follows the way the main build is carried out, certain parameters need to be cleared. In particular, the computed root is not part of the rebuild and no build output should be dumped anywhere. | |||
2024-12-11 | main: avoid spourious warnings | Klaus Aehlig | |
... given that a proper reporting of the return code if repo_config.SetGitCAS is contained in main anyway. Therefore, log the details trying to set the git cas to a level less than that of the final reporting. | |||
2024-12-11 | RepositoryConfig::SetGitCAS: allow setting log_level | Klaus Aehlig | |
... as there might be cases where it is expected that setting the git CAS fails, e.g., if referring to the implict git repository in the local build root as a fallback CAS. | |||
2024-12-11 | GitCAS::Open: allow specifying the log-level for failure | Klaus Aehlig | |
This method returns a GitCASPtr allowing the caller to handle failure gracefully. Therefore, logging should be at most at level Warning as it is up to the caller to provide the fatal error message. Moreover, it can be at lower level in cases where failure to open that git cas is not an unexpected event, e.g., when looking for a blob in local mirrors first. | |||
2024-12-11 | computed root building: synchronize log to remote in case of failure | Klaus Aehlig | |
When materializing a computed root fails, the error is reported as a reference (in form of a blob identifier) to the log. This indirection is necessary as many roots are, in general materialized simultaneously. When building remotely, also upload the build log to remote execution; in this way, it is available in the same way as for serve-build failures (which are the other delegated builds). One particular use case is if the failure happens on a CI build; then the upload ensures the actual log is still available for the observer of the CI (provided they have access to the remote execution used by the CI). | |||
2024-12-10 | Computed Roots: be aware of the serve end point | Klaus Aehlig | |
... as the base repository of a computed root might be absent. | |||
2024-12-10 | just-mr launch: Pass local launcher to just analyse | Paul Cristian Sarbu | |
2024-12-09 | Computed roots: only install artifacts | Klaus Aehlig | |
... however, also build the runfiles, as they are needed to write the target-level cache for the underlying export target. | |||
2024-12-09 | Avoid writing to the CAS during bootstrapping | Maksim Denisov | |
2024-12-09 | Move compactifier to a separate library | Maksim Denisov | |
2024-12-09 | Move garbage_collector to a separate library | Maksim Denisov | |
2024-12-09 | Remove redundant copies from BazelApi::IsAvailable | Maksim Denisov | |
...and ignore non-requested digests. | |||
2024-12-09 | Use expected to return an error from ParseRoot | Maksim Denisov | |
2024-12-09 | Localize error_msg argument of ParseRoot | Maksim Denisov | |
...and use expected to replace it. | |||
2024-12-09 | analysis: Support artifact build arguments | Paul Cristian Sarbu | |
As analysis now can compute roots, i.e., can build artifacts, it needs to support setting the local launcher, action timeout, and the build jobs. The stage and rebuild arguments, which are also needed by the graph traversal, as well as other build-related arguments, remain not supported for the analysis subcomamnd, however they remain honored if set by subcommands that trigger an implicit analysis (e.g., build or install). | |||
2024-12-09 | computed-roots/evaluate: Fix typos in log messages | Paul Cristian Sarbu | |
2024-12-06 | executor: On failure to execute an action, also report which action it was | Klaus Aehlig | |
Failure to execute an action can be infrastructure problems, like failure to reach the server, etc. However, it can also be an action timeout; in the latter case, we want to know which action it was that did time out. | |||
2024-12-06 | Cleanup dependencies | Klaus Aehlig | |
2024-12-06 | Log: report outputs of failed actions by default | Klaus Aehlig | |
Some actions are allowed to fail, typically tests. By reporting the output of failed such actions early, the user can already have a look at those artifacts, typically a test log, while the build is still going on. | |||
2024-12-05 | Also for installation to stdout prefer local CAS | Klaus Aehlig | |
... to avoid unnecessary network fetches. | |||
2024-12-05 | While there, also avoid unnecessary indirection in RertrieveToPaths. | Klaus Aehlig | |
2024-12-05 | execution api: support retrieving from more than one API, also for fd | Klaus Aehlig | |
Extend the api to optionally accept a different API for preferred fetching. This is already supported when fetching to a file path; therefore, extend to keep the interface symmetric. |