~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
2025-02-05	CHANGELOG: mention local-api fix	Klaus Aehlig

2025-02-05	Add basic end-to-end test for just-mr gc --drop-only	Klaus Aehlig

2025-02-05	just-mr(1): Document new option --drop-only for gc-repo	Klaus Aehlig

2025-02-05	just-mr gc-repo: support drop only	Klaus Aehlig
	As opposed to the regular CAS/cache, for the git repository implicit in the repository cache we cannot guarantee that data from older generation is always promoted via hard links. Therefore, a certain amount of data can be duplicated between the repo-cache generations. In order to allow compacting storage to the minimum, add an option to gc-repo to only remove the older generation, without rotating.
2025-02-05	Repository garbage collector: support dropping only	Klaus Aehlig
	Add support for repository gargabe collection to only drop the older generations without rotating.
2025-02-05	just-mr(1): document the gc-repo subcommand	Klaus Aehlig

2025-01-30	README: fix reference to tutorial section	Klaus Aehlig

2025-01-30	Add basic introduction on how to set up computed roots	Klaus Aehlig

2025-01-30	CHANGELOG: document recent fix to `just-mr gc-repo`	Klaus Aehlig

2025-01-30	Add an end-to-end test for repeated repository garbage collection	Klaus Aehlig
	As only a recent commit made it possible to rotate the repository cache more than once, add a test ensuring two properties. - Repeated repository gc is possible and roots are taken from the rotated generation. - It is possible to fully rotate a root out.
2025-01-29	local api: absence of a git api is not a success in retrieving	Klaus Aehlig
	While there, also check for availability first, to avoid duplicated error messages (from git_cas and the caller).
2025-01-29	just-lock: Search for archives to fetch also in Git cache	Paul Cristian Sarbu
	...before trying remotes.
2025-01-29	just-lock: Run commit check command only on existing repositories	Paul Cristian Sarbu
	While there, improve docstrings of methods operating on Git repositories to specify when the underlying Git repositories are expected to be present.
2025-01-29	just-lock: Add support for 'tree structure' roots	Paul Cristian Sarbu
	Based on f0473730 and 22ef0a16
2025-01-29	just-lock: Fix deduplication of 'computed' roots	Paul Cristian Sarbu
	Based on 76ce2123
2025-01-29	just-lock: Normalize subdir before checking if non-upward	Paul Cristian Sarbu

2025-01-29	just-lock: Improve error handling for importing to Git	Paul Cristian Sarbu

2025-01-29	just-lock: Ensure all commands use the run_cmd method	Paul Cristian Sarbu

2025-01-29	just-deduplicate-repos: Fix formatting	Paul Cristian Sarbu

2025-01-29	just-lock-config(5): Document the 'git tree' source type	Paul Cristian Sarbu

2025-01-29	just-lock config: Make field names consistent with just-mr	Paul Cristian Sarbu

2025-01-29	garbage collection: remove garbage recursively	Klaus Aehlig
	When garbage collecting the oldest generation, we expect it to be a non-empty directory. Therefore, remove it recursively.
2025-01-28	Progress reporting: also report the primary action output	Klaus Aehlig
	While reporting an origin target with action number within that target describes an action uniquely in a way meaningful to the user, it might not always be eay to unserstand which precise action is currently running. For example, for a library with many source files, we have a target generating a large number of actions and the association of source file to action number requires detailled knowledge of the build description. The name of the primary ouput of that action, on the other hand immediately identifies the file that is compiled. Therefore, report this as well.
2025-01-27	Update libfmt to 11.1.3	Klaus Aehlig

2025-01-24	Add native comparison of configured targets	Klaus Aehlig
	... and use it when normalizing the origins of actions. For this task, any well-defined linear order is sufficient. Using a native comparision (rather than comparing the canonical serialisation) significantly speeds up that normalisation process, as the assumption that it would be rare that an action has more than one origin turned out to be false. In fact, we have seeen cases where this sorting used to take several seconds before this change, so that this change reduced analysis time by more than a factor of 5.
2025-01-24	Action equality test: only verify the set of origins	Klaus Aehlig
	While our tool promises to generate a reproducible order of the action origins, we should not insist on a particular one. Therefore sort before comparing.
2025-01-24	Add test verifying the "generic" rule properly detecs staging conflicts	Klaus Aehlig

2025-01-24	"generic" rule: verify staging conflicts on inputs	Klaus Aehlig
	The "generic" rules deliberately resolves conflicts on identical paths in a latest-wins fashion (seeing all artifacts as later than all runfiles) to allow an easy way to define actions. However, the inputs stage obtained by this resolution can still contain conflicts and those are an error. Properly detect those. Also clarify in the documentation, that only conflicts on identical paths are resolved in the described priority, not semantic overlap.
2025-01-23	Add basic end-to-end test on progress reporting	Klaus Aehlig

2025-01-23	Computed roots: add basic progress reporting	Klaus Aehlig

2025-01-23	Add basic progress reporter on root evaluation	Klaus Aehlig

2025-01-23	Remove unused library "root_utils"	Maksim Denisov

2025-01-23	JustMr: Replace calls to CheckServeHasAbsentRoot with direct calls to serve	Maksim Denisov

2025-01-23	PrecomputedRoot: Remove DownloadFromServe	Maksim Denisov
	... and replace it with a direct call to serve.
2025-01-23	ServeApi: Implement DownloadTree	Maksim Denisov

2025-01-23	PrecomputedRoots: Remove UploadToServe	Maksim Denisov
	... and replace it with a direct call to serve.
2025-01-23	Remove function EnsureAbsentRootOnServe	Maksim Denisov
	...since it is superseded by ServeApi's method.
2025-01-23	JustMr: ContentGitMap: Remove unused arguments.	Maksim Denisov

2025-01-23	JustMr: ContentGitMap: Use serve calls	Maksim Denisov
	...instead of EnsureAbsentRootOnServe.
2025-01-23	JustMr: ContentGitMap: Remove code duplication.	Maksim Denisov

2025-01-23	JustMr: DistdirGitMap: Use serve calls	Maksim Denisov
	...instead of EnsureAbsentRootOnServe. And remove unused arguments.
2025-01-23	JustMr: CommitGitMap: Remove unused arguments.	Maksim Denisov

2025-01-23	JustMr: CommitGitMap: Use serve calls	Maksim Denisov
	...instead of EnsureAbsentRootOnServe.
2025-01-23	JustMr: FilePathGitMap: Remove unused arguments.	Maksim Denisov

2025-01-23	JustMr: FilePathGitMap: Use serve calls	Maksim Denisov
	...instead of EnsureAbsentRootOnServe
2025-01-23	ServeApi: Implement UploadTree	Maksim Denisov

2025-01-23	ServeApi: Capture ApiBundle and StorageConfig in the ctor.	Maksim Denisov

2025-01-23	Call serve directly instead of EnsureAbsentRootOnServe.	Maksim Denisov

2025-01-23	Document computed roots as implemented concept	Klaus Aehlig
	... rather than as future design. While there, also add target-level caching as a service to the list of documentation pages.
2025-01-22	Git CAS access: reduce log level	Klaus Aehlig
	Trying to access a git object return a recoverable failure, hence the failure to find the object in the git object database should be logged at warning level at most. Moreover, in some cases we should log that event at an even lower level, e.g., if we're just checking the presence of the object in the local git cas to avoid unnecessary network access.