| Age | Commit message (Collapse) | Author |
|---|
|
It is already supported to ask just-mr (via the rc file) to log for
each invocation the artifacts that were built. Add a similar option
for the artifacts that were to be built, i.e., for dumping the
intensional description of the output artifacts. That information
can be used, e.g., to compute the critical path.
|
|
It allows to specify a list of environment variables, which are captured at
invocation time and stored as key-value pairs in the metadata file. This allows
to get some information about the invocation context such as username,
merge-request ID or source branch (on a CI runner), or others.
|
|
|
|
|
|
Allow to specify a custom string that is extended by the basename
of the logging directory, in case invocation logging is activated.
This can be used, e.g., to point to the user to service doing
something useful with the logged data (or simply presenting it in
a nicer form).
|
|
Support passing on an invocation-specific --profile option
when launching just. This allows routine profiling of builds.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
With "remote-execution properties" a primary property, there is no need
anymore to repeat the property as part of the "just args".
|
|
While just-mr does not use remote-execution properties, it is
still useful to have those as a separate entry in the rc file. With
rc-file delegation, this gives committed rc files an easy way to
specify the image to be used without having to set all the remaining
arguments for the various just subcommands in "just args".
|
|
... to pull in rc files from different locations, given by
location objects.
|
|
When just-mr acts as a launcher, for most subcommand options the
"just args" entry in the rc files provides a convenient way to set
them. However, some options take a file as argument; for those it can
be desirable to set them without assuming a fixed file-system layout
and instead refer to logical roots, in particular the work space.
for the ones that refer to files, it is often desirable to have a potential
reference to the work space. Add this functionality.
|
|
... those are actually given as location objects, not as plain paths.
|
|
|
|
|
|
Using absent repositories depends on a just-serve endpoint. As
such, it is not a datum of the project, but one of the available
infrastructure. As the latter can change independently of the
project, it is desriable to have the option to specify those pieces
of information in separate files.
|
|
As we have, with "remote execution", a command-independent option to
set the remote-execution endpoint that also gets forwarded, a typical
configuration would specify the endpoint there.
|
|
|
|
with the remote execution address and mTLS authentication options.
|
|
|
|
|
|
|
|
pages
In order to consistently emphasize arguments and other keywords in man page as
well as markdown viewers, they should be wrapped in single asterisks and single
backticks like *`<argument>`*.
|
|
|
|
... for easy processing with pandoc.
|
