summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2024-11-21Add basic test for computed rootsKlaus Aehlig
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
2024-11-21RepositoryConfig: support setting a computed rootKlaus Aehlig
2024-11-21Add data structure for the description of a computed rootKlaus Aehlig
2024-11-20Return ResultTargetMap from analysisMaksim Denisov
...instead of filling in a map passed from the outside.
2024-11-20Serve service: properly lock git operations against each otherKlaus Aehlig
... by using an exclusive lock. A lock of which only ever shared instances are requested has no synchronisation effect. Fix this.
2024-11-14tests: Implement IWYU suggestionsMaksim Denisov
2024-11-14utils: Implement IWYU suggestionsMaksim Denisov
2024-11-14other_tools/utils: Implement IWYU suggestionsMaksim Denisov
2024-11-14other_tools/repo_map,root_maps: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14other_tools/ops_maps: Implement IWYU suggestionsPaul Cristian Sarbu
Also follow-up changes to ensure build success.
2024-11-14other_tools/just_mr: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14other_tools/git_operations: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14system: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14storage: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14serve_api: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14progress_reporting: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14multithreading: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14main: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14logging: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14graph_traverser: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14file_system: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14execution_engine: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14execution_api remaining: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14execution_api/remote: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14execution_api/execution_service: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14crypto: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14common: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14build_engine: Implement IWYU suggestionsPaul Cristian Sarbu
Requires the use of a pragma to avoid wrong removal suggestion for path_hash.hpp. Co-authored-by: Maksim Denisov <denisov.maksim@huawei.com>
2024-11-14auth: Implement IWYU suggestionsPaul Cristian Sarbu
2024-11-14clang-format: Update config filePaul Cristian Sarbu
The base style already handles correctly the system includes, so one needs to only add regex expressions to handle third-party and own includes. This fixes also the include formatting of git_config_run.test.cpp.
2024-11-14tpp includes: Add hint for IWYU lintingPaul Cristian Sarbu
IWYU needs to be explicitly instructed how to handle included .tpp files in order to not falsely suggest their removal. Conversely, it also needs to know not to suggest including .tpp files instead of the corresponding .hpp files.
2024-11-14target_cache_key: Move hash definition to class headerPaul Cristian Sarbu
2024-11-13RepositoryConfig: get rid of implict usage assumptionKlaus Aehlig
The class RepositoryConfig is mutable, but has a set-once derived value, the largest bisimulation of the repositories described. This construction is problematic in that it assumes that all modifications be done before the first inspection of a value happens that implicitly triggers the setting of the derived value. Therefore, at the very least reset this derived value if a repository is modified.
2024-11-13just main: subcommand traverse should only traverseKlaus Aehlig
... regardless of success. If traversing fails, we should just return failure. In this way, we can also avoid an unnecessary else-branch. While there, always return normally for tarverse, avoiding direct exits.
2024-11-11["lint", "targets"]: support reporting the name of the linting performedKlaus Aehlig
2024-11-11repository-config(5): document the possibility of absent rootsKlaus Aehlig
2024-11-08Design computed roots: Add additional root typeKlaus Aehlig
... specifically for the use case of target files depending on the directory structure.
2024-11-06Use "cwd" property of actionsKlaus Aehlig
... instead of composing a shell command doing a cd first.
2024-11-06Use quote and quasi-quote to simplify some expressionsKlaus Aehlig
2024-11-06Prefer built-in "nub_left"Klaus Aehlig
Now that justbuild 1.4 is available, the workaround of defining "nub_left" in terms of "reverse" and "nub_right" is no longer necessary.
2024-11-06Make bootstrap-traverser aware of the "cwd" property of actionsKlaus Aehlig
2024-11-04Start 1.5 development cycleKlaus Aehlig
2024-11-04Release 1.4.0v1.4.0Klaus Aehlig
2024-10-31["lint", "targets"]: support TMPDIRKlaus Aehlig
2024-10-30Release 1.4.0~beta1v1.4.0-beta1Klaus Aehlig
2024-10-30CHANGELOG: mention cooperation of `just serve` with compatible remoteKlaus Aehlig
2024-10-30Update to grpc v1.67.1Paul Cristian Sarbu
Update also direct dependencies: - boringssl b8b3e6e - google_apis fe8ba05 - protobuf v27.2 Also update the bootstrap build description for crypto library. Remove ssl patch for gcc-14 build as fix is now in upstream. Remove bytestream.proto patch as fix is now in upstream. Target utf8_range now taken only from protobuf, where it is first defined. For now, upb dependencies in grpc still taken from its own third_party subdirectory, as it is still kept synchronized with the corresponding tree in the corresponding protobuf version.
2024-10-29Graph traverser: fix wrong wording in trace-level messageKlaus Aehlig
As we write the first message about the actual upload of a blob, we should use future rather than past tense. Also, again at trace level, add a message of successful completion, if we succeeded.