summaryrefslogtreecommitdiff
path: root/src/buildtool/computed_roots/TARGETS
AgeCommit message (Collapse)Author
2025-02-28Make statistics a separate libraryMaksim Denisov
2025-02-28Include ArtifactDigestFactory into "common" libraryMaksim Denisov
2025-02-19ApiBundle: Remove HashFunction.Maksim Denisov
And ensure every user obtains HashFunction from corresponding IExecutionApi
2025-01-23Computed roots: add basic progress reportingKlaus Aehlig
2025-01-23Add basic progress reporter on root evaluationKlaus Aehlig
2025-01-23PrecomputedRoots: Remove UploadToServeMaksim Denisov
... and replace it with a direct call to serve.
2025-01-22absent computed roots: obtain value from serve without fetching artifactsKlaus Aehlig
2025-01-21Implement UploadToServeMaksim Denisov
2025-01-21TreeStructureUtils: implement local computation of tree structureMaksim Denisov
2025-01-21TreeStructureUtils: export from gitMaksim Denisov
2025-01-21Rename compute_tree_structure to tree_structure_utilsMaksim Denisov
2025-01-15Use GitRepo::IsTreeInRepo during evaluation of precomputed roots.Maksim Denisov
2024-12-19TreeStructure: evaluate roots.Maksim Denisov
2024-12-19Use PrecomputedRoots during evaluationMaksim Denisov
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-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-06Cleanup dependenciesKlaus Aehlig
2024-12-04Cache lookup: support rehash functionKlaus Aehlig
2024-12-04ArtifactsRoot: support rehash-functionKlaus Aehlig
When constructing a git tree out of an artifact stage, support rehashing the artifact digests on the fly, so that artifact stages not based on GitSHA1 can be supported as well.
2024-11-29Clean up unused depsKlaus Aehlig
2024-11-28computed roots: restrict in-memory root computation to the supported casesKlaus Aehlig
... and, in this way, avoid git-tree computations with invalid git identifiers.
2024-11-28computed roots: properly report failure to materialize rootsKlaus Aehlig
2024-11-27computed roots: enforce export targets of content-fixed reposKlaus Aehlig
... and look up values in cache, if possible.
2024-11-27Add a library computing, in memory, a git tree from a stageKlaus Aehlig
Computed roots are given as the artifacts stage of a target. However, to be usable as a root, we need the git tree identifier of that root. Therefore, add a library doing this computation, avoiding file-system operations whenever possible.
2024-11-22AnalyseAndBuild: also write target-level cache entriesKlaus Aehlig
While there, also clean up the analysis result as soon as it is no longer needed.
2024-11-21Materialize computed roots before top-level analysisKlaus Aehlig
Add a basic implementation of computed roots. So far we neither enforce nor make good use of the fact that the underlying target of a computed root has to be an export target of a content-fixed repository; instead, we always install the root to a temporary directory and pick it up from there. Still, the basic functionality is there, and it is minimally useful.
2024-11-21Implement AnalyseAndBuild functionMaksim Denisov