~aehlig/just-buildsystem/justbuild.git - Main repository of just-buildsystem, containing the buildtool (just) in bootstrappable form, the multi-repository setup and launch tool (just-mr) and some auxilliary tools.

Age	Commit message (Collapse)	Author
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.
2024-12-05	Common API: correctly report failure	Klaus Aehlig
	If fetching via the primary API failed and there is no fallback, we should fail rather than tacitly continuing with the next object to fetch.
2024-12-05	GitCAS: remove friend GitRepo	Maksim Denisov
	...and access internal state via getters.
2024-12-05	GitCAS: remove mutex and locks	Maksim Denisov
	...since there are no unique_locks any more.
2024-12-05	GitRepo: don't reassign git_repository to git_odb	Maksim Denisov
	...and remove GuardedRepo.
2024-12-05	GitCAS: retain git_repository alive.	Maksim Denisov

2024-12-05	GitCAS: implement method for creation of an empty GitCAS	Maksim Denisov
	...and use it in GitRepo to set custom backends.
2024-12-05	GitCAS: remove redundant method	Maksim Denisov

2024-12-05	GitCAS: avoid manual memory management	Maksim Denisov
	...and fix a potential memory leak in the try-catch for std::filesystem::absolute.
2024-12-05	GitCAS: use the same call for openning repository as GitRepo does.	Maksim Denisov

2024-12-05	GitRepo: keep GuardedRepo unexposed and adjust the interface.	Maksim Denisov

2024-12-04	Rehash root lookup, if building in compatible mode	Klaus Aehlig
	To avoid unnecessary staging and git imports of computed roots for build in compatible mode, use the rehashing functionality to allow us to compute the git tree of that root in memory.
2024-12-04	Cache lookup: support rehash function	Klaus Aehlig

2024-12-04	ArtifactsRoot: support rehash-function	Klaus 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-12-04	rehash_utils: add a class for the rehash function	Klaus Aehlig
	... to allow a more specific signature when passing around the rehash function.
2024-12-04	Add deep rehashing from bazel::Directories to Git	Maksim Denisov

2024-12-04	BazelMsgFactory: Add method to create Git tree from bazel Directory	Paul Cristian Sarbu

2024-12-04	Add RehashGitDigest function	Maksim Denisov

2024-12-04	Add RehashDigest function	Maksim Denisov

2024-12-04	Rename MRApiUtils to RehashUtils	Maksim Denisov

2024-12-03	For FetchIntoODBBackend "Ensure" backend is valid	Maksim Denisov

2024-12-03	Avoid double deletion of git_repository in GuardedRepo	Maksim Denisov

2024-12-03	JustMR: add computed overlay repos to reachable	Maksim Denisov

2024-12-03	JustMR: treat computed roots like any other repository	Maksim Denisov
	...and process their bindings.
2024-12-03	JustMR: process overlay repositories during traverse	Maksim Denisov
	...and remove the second for-loop.
2024-12-03	JustMR: replace recursion in traverse with a for-loop	Maksim Denisov

2024-12-02	Synchronize initialization of a git repo across processes	Maksim Denisov

2024-12-02	Add aditional checks to initializations of git repos	Maksim Denisov

2024-12-02	Replace default value of GitOpValue's result field by std::nullopt.	Maksim Denisov