~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-06-27	Use a raw pointer for passing optional RepositoryConfig	Maksim Denisov
	...instead of std::optional<gsl::not_null<RepositoryConfig const*>>.
2024-06-27	Use a raw pointer for passing optional IExecutionApi	Maksim Denisov
	...instead of std::optional<gsl::not_null<IExecutionApi const*>>
2024-06-26	just: shorten repeated mentioning of the top-level target	Klaus Aehlig
	The build tool prints status messages at the end of each of the major stages that sequentially follow each other. This allows, in particular when using log files (that contain time stamps) to quickly identify which phase was the resource consuming one. All these message mention the (same!) configured target that is process by this invocation of the build tool. In the presence of toolchains, the configuration can, however, get quite large (containing lots of paths to various tools). Therefore, shorted the configuration in the repeated menions if it is very long (currenlty 320 characters); as we do not change the first mentinoing ("Requested target is ..."), even with that shortening the log contains the same information.
2024-06-25	describe: also describe "configure" targets in more detail	Klaus Aehlig
	Most built-in rules are just described by their name, assuming they are known to the user anyway. One exception, however, are "export" targets, as those serve as interfaces to (logical) repositories and hence is supposed to have a documentation of the target itself. Over time, however, "configure" targets have evolved to become internal interfaces (maybe even for an external target), e.g., to provide default values and hence make better use of the actual export target. Therefore it is desirable to provide a bit more information when asked to describe a "configure" target. - As "configure" targets have a fixed set of keys, adding a "doc" field is a conservative extension; this can be useful to give an overview what the target is about. - An important information of a "configure" target is the target that is configured. While this, in general, is an expression, in the typical cases, the description is very short (a literal target name, or a variable). So we can afford to show the definition.
2024-06-25	Introduce a type allias for an optional ptr to IExecutionApi	Maksim Denisov
	...and replace verbose constructions.
2024-06-25	Make IExecutionApi::Ptr a shared pointer to const	Maksim Denisov
	...and use it in ApiBundle.
2024-06-25	Use constant IExecutionApi in just-mr maps	Maksim Denisov

2024-06-25	Pass IExecutionApi to ServerImpl, Archive by reference	Maksim Denisov
	...instead of not_null const ptr.
2024-06-25	Pass IExecutionApi to Executor by referece	Maksim Denisov
	...instead of not_null const ptr.
2024-06-25	Pass IExecutionApi to IExecutionApi by reference	Maksim Denisov
	...instead of not_null const ptr.
2024-06-25	Mark IExecutionApi's methods constant	Maksim Denisov

2024-06-25	Remove CreateExecutionApi	Maksim Denisov

2024-06-25	Pass ApiBundle to ServerImpl	Maksim Denisov

2024-06-25	Pass ApiBundle to describe	Maksim Denisov

2024-06-25	Pass ApiBundle to add-to-cas and install-cas	Maksim Denisov

2024-06-25	Pass ApiBundle to SourceTreeService	Maksim Denisov

2024-06-25	Pass ApiBundle to ServeApi	Maksim Denisov

2024-06-25	Use ApiBundle for creation of APIs in just-mr	Maksim Denisov

2024-06-25	Pass ApiBundle to GraphTraverser	Maksim Denisov

2024-06-25	Instantiate LocalApi and BazelApi at once	Maksim Denisov
	...to properly fallback to local api if needed.
2024-06-25	Use a general boolean for compatible in MultiRepoCommonArguments	Maksim Denisov

2024-06-25	Remove GraphTraverser's constructor used for tests only.	Maksim Denisov

2024-06-18	Make ServeServerImpl a general class, not a singleton.	Maksim Denisov

2024-06-18	Make RemoteServeConfig a general struct, not a singleton	Maksim Denisov
	...and adjust interfaces.
2024-06-18	Create an individual instance of RemoteServeConfig in just-mr	Maksim Denisov
	...instead of initialization of the singleton.
2024-06-18	Create an individual instance of RemoteServeConfig in just	Maksim Denisov
	...instead of initialization of the singleton. Use builder for creation and validity check.
2024-06-18	Make ServeApi a general class, not a singleton	Maksim Denisov
	...and adjust interfaces.
2024-06-18	Pass RemoteAddress to ConfigurationClient by value	Maksim Denisov
	...instead of using singleton calls.
2024-06-18	Pass ServeApi to just-mr maps by reference	Maksim Denisov
	...instead of using singleton calls.
2024-06-18	Pass ServeApi to ServeServerImpl by reference	Maksim Denisov
	...instead of using singleton calls.
2024-06-18	Pass RemoteServeConfig to ServeServerImpl by reference	Maksim Denisov
	...instead of using singleton calls.
2024-06-18	Pass ServeApi by reference to the describe function	Maksim Denisov
	...instead of using singleton calls.
2024-06-18	Pass ServeApi as a field of context to the analysis	Maksim Denisov
	...instead of using singleton calls.
2024-06-18	Use ServeApi during bootstrap	Maksim Denisov
	...with a default implementation. Although it is not used directly, it will be needed for instantiation of std::optional.
2024-06-18	Use an extensible structure to pass arguments to the analysis.	Maksim Denisov

2024-06-18	Store services in ServeApi by value.	Maksim Denisov
	* No stackoverflow is possible: there is just one instance of ServeApi and services are relatively 'light'; * Services are not optional and cannot be changed during their use; * operator-> is not free.
2024-06-18	Mark ServeApi's services' methods contant.	Maksim Denisov

2024-06-18	Use RemoteServeConfig functionality via Instance()	Maksim Denisov
	...to track changes during refactoring easier.
2024-06-18	Use ServeApi functionality via Instance()	Maksim Denisov
	...to track changes during refactoring easier.
2024-06-17	Use c++20 standard in clang-format	Maksim Denisov

2024-06-17	executor: properly separate stdout and stderr in log messages	Klaus Aehlig
	... about processes producing both, stdout and stderr. By supporting unique readability of the output, we facilitate the understanding of the messages provided by actions.
2024-06-17	Add utility function for prefixing each line of a string	Klaus Aehlig
	... and thus allowing proper quoting of command output.
2024-06-11	Move creation of TargetCacheKey description to TargetCache	Maksim Denisov
	...to use corresponding Storage for storing auxiliary information.
2024-06-07	Move reading functionality to BazelNetworkReader	Maksim Denisov
	...to enable validation of received blobs.
2024-06-07	Validate all blobs received over the network.	Maksim Denisov

2024-06-07	Use BaselCasClient in BazelNetworkReader	Maksim Denisov
	...bypassing BazelNetwork layer.
2024-06-07	Mark methods constant in BazelCasClient.	Maksim Denisov

2024-06-07	Remove unused code	Maksim Denisov

2024-06-07	Remove unused code.	Maksim Denisov
	IExecutionApi::UploadFile was introduced to handle adding of a temporary file to the storage. The call was redirected to LocalCAS internal methods that do the similar thing, so this virtual method can be removed.
2024-06-06	tc writing: allow different log level	Klaus Aehlig
	... for failures instead of the binary strict_logging. In this way, we can log at log level Error in the serve instance, and for the client at level Warning or Info, depending on whether failure is expected (i.e., if targets are potentially taken from a serve endpoint) or not.