summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2025-01-07Add backend description to CAS in a ctor of TargetCacheMaksim Denisov
...instead of adding it preliminarily.
2025-01-07TargetCache: use BackendDescription for sharding instead of a plain stringMaksim Denisov
2025-01-07Store BackendDescription in StorageConfigMaksim Denisov
...instead of a plain hash. Hash gets computed for different storage types on the fly.
2025-01-07TargetCache: employ the shard even for a default constructed objectMaksim Denisov
...since this is a more generic approach.
2025-01-07Pass BackendDescription to StorageConfig from the outsideMaksim Denisov
2025-01-07Pack BackendDescription to a classMaksim Denisov
...to let it be stored as an independent instance.
2024-12-20clean up dependenciesKlaus Aehlig
2024-12-20TreeStructure: make just-mr aware of "tree structure" rootsMaksim Denisov
2024-12-20TreeStructure: support parsing in just-mrMaksim Denisov
2024-12-20TreeStructure: Unify parsing of precomputed roots in just-mrMaksim Denisov
2024-12-19TreeStructure: evaluate roots.Maksim Denisov
2024-12-19TreeStructure: Implement computation logicMaksim Denisov
2024-12-19TreeStructure: Implement cache with uplinkingMaksim Denisov
2024-12-19Implement TreeStructureRootMaksim Denisov
2024-12-19FileRoot: disclose RootGit data.Maksim Denisov
2024-12-19Move functionality for staging from CAS to output paths to TreeReaderMaksim Denisov
...and employ it in LocalApi.
2024-12-19Remove FileRoot::ComputedRootMaksim Denisov
2024-12-19Use PrecomputedRoots during evaluationMaksim Denisov
2024-12-19Support substitution of precomputed roots in RepositoryConfigMaksim Denisov
2024-12-19Support PrecomputedRoots in FileRootMaksim Denisov
2024-12-19Implement PrecomputedRootsMaksim Denisov
...that is an abstract representation of roots that must be computed before the start of the main build.
2024-12-19Fix cause of minor warningsOliver Reiche
2024-12-19Fix struct member initializationOliver Reiche
2024-12-19Remove unused headersOliver Reiche
2024-12-19Remove unused functionOliver Reiche
2024-12-19Remove unneeded compat_storageOliver Reiche
2024-12-19Remove unnecessary movesOliver Reiche
2024-12-19JustMr: update output config for computed rootsMaksim Denisov
2024-12-12Computed roots: normalize build argumentsKlaus 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-11main: avoid spourious warningsKlaus 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-11RepositoryConfig::SetGitCAS: allow setting log_levelKlaus 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-11GitCAS::Open: allow specifying the log-level for failureKlaus 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-11computed root building: synchronize log to remote in case of failureKlaus 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-10Computed Roots: be aware of the serve end pointKlaus Aehlig
... as the base repository of a computed root might be absent.
2024-12-10just-mr launch: Pass local launcher to just analysePaul Cristian Sarbu
2024-12-09Computed roots: only install artifactsKlaus Aehlig
... however, also build the runfiles, as they are needed to write the target-level cache for the underlying export target.
2024-12-09Avoid writing to the CAS during bootstrappingMaksim Denisov
2024-12-09Move compactifier to a separate libraryMaksim Denisov
2024-12-09Move garbage_collector to a separate libraryMaksim Denisov
2024-12-09Remove redundant copies from BazelApi::IsAvailableMaksim Denisov
...and ignore non-requested digests.
2024-12-09Use expected to return an error from ParseRootMaksim Denisov
2024-12-09Localize error_msg argument of ParseRootMaksim Denisov
...and use expected to replace it.
2024-12-09analysis: Support artifact build argumentsPaul 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-09computed-roots/evaluate: Fix typos in log messagesPaul Cristian Sarbu
2024-12-06executor: On failure to execute an action, also report which action it wasKlaus 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-06Cleanup dependenciesKlaus Aehlig
2024-12-06Log: report outputs of failed actions by defaultKlaus 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-05Also for installation to stdout prefer local CASKlaus Aehlig
... to avoid unnecessary network fetches.
2024-12-05While there, also avoid unnecessary indirection in RertrieveToPaths.Klaus Aehlig
2024-12-05execution api: support retrieving from more than one API, also for fdKlaus 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.